A aviation & planes forum. AviationBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » AviationBanter forum » rec.aviation newsgroups » Instrument Flight Rules
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

When to descend



 
 
Thread Tools Display Modes
  #1  
Old October 10th 07, 12:58 AM posted to rec.aviation.ifr
Ron Rosenfeld
external usenet poster
 
Posts: 264
Default When to descend

On Tue, 09 Oct 2007 14:27:34 -0500, Mitty wrote:

Why would you read anything into it? I'm not being argumentative; I just don't
understand why you would not "maintain 4000' until established" and at that
point begin to descend. Or, if you didn't like the profile, get back to ATC and
"request lower."


When you enter the TAA, you ARE established.
Ron (EPM) (N5843Q, Mooney M20E) (CP, ASEL, ASES, IA)
  #2  
Old October 10th 07, 02:15 AM posted to rec.aviation.ifr
Bee
external usenet poster
 
Posts: 29
Default When to descend

Mitty wrote:



On 10/9/2007 1:20 PM, Steven P. McNicoll wrote the following:



He doesn't say whether this is an actual clearance received or a
hypothetical scenario. The book phraseology would be, "Cleared to UDUZI,
maintain four thousand until entering the TAA, cleared RNAV runway niner
left approach." If he's already crossed the TAA boundary the clearance
would be just, "Cleared RNAV runway niner left approach."


"Cleared direct UDUZI, maintain 4000' until established, cleared RNAV 9L
approach." sounds like a lot of clearances I have received. Possibly
not by the book verbiage, but real world IMHO.

Why would you read anything into it? I'm not being argumentative; I
just don't understand why you would not "maintain 4000' until
established" and at that point begin to descend. Or, if you didn't like
the profile, get back to ATC and "request lower."

It could be that ATC had crossing traffic at 3000' -- no?

You are established when you enter the TAA.
  #3  
Old October 10th 07, 12:56 AM posted to rec.aviation.ifr
Ron Rosenfeld
external usenet poster
 
Posts: 264
Default When to descend

On Tue, 9 Oct 2007 13:20:14 -0500, "Steven P. McNicoll"
wrote:

He doesn't say whether this is an actual clearance received or a
hypothetical scenario. The book phraseology would be, "Cleared to UDUZI,
maintain four thousand until entering the TAA, cleared RNAV runway niner
left approach." If he's already crossed the TAA boundary the clearance
would be just, "Cleared RNAV runway niner left approach."


Exactly.
Ron (EPM) (N5843Q, Mooney M20E) (CP, ASEL, ASES, IA)
  #4  
Old October 10th 07, 02:14 AM posted to rec.aviation.ifr
Bee
external usenet poster
 
Posts: 29
Default When to descend

Ron Rosenfeld wrote:

On Tue, 9 Oct 2007 10:09:26 -0500, "Dan Luke"
wrote:


You are coming from northeast of SFB. ATC says "Cleared direct UDUZI,
maintain 4000' until established, cleared RNAV 9L approach."

http://www.naco.faa.gov/d-tpp/0710/00917R9L.PDF


When do you descend below 4,000 and to what altitude?



Coming from the NE, you may descend to 2700' after crossing 30 NM from
UDUZI (in the Left Base Area of the TAA).

Since there seems to be some variation in the responses to your question,
here is the relevant AIM paragraph:

Pilots entering the TAA and cleared by air traffic control, are expected
to proceed directly to the IAF associated with that area of the TAA at the
altitude depicted, unless otherwise cleared by air traffic control. Cleared
direct to an Initial Approach Fix (IAF) without a clearance for the
procedure does not authorize a pilot to descend to a lower TAA altitude.

Perhaps the controller should have said "...maintain 4000 until entering
the TAA". But I think his intent is clear. If he wanted you at 4000 until
crossing UDUZI, he should have either stated that explicitly, or not
cleared you for the approach.
Ron (EPM) (N5843Q, Mooney M20E) (CP, ASEL, ASES, IA)


I guess the AIM and the IPH need to state "A TAA straight-in, left base,
or right base area is the regulatory equivalent of a published approach
segment." Otherwise, the uncertainty and sharpshooting is endless. ;-)
  #5  
Old October 10th 07, 02:30 PM posted to rec.aviation.ifr
Dan Luke[_2_]
external usenet poster
 
Posts: 713
Default When to descend


"Bee" wrote:

I guess the AIM and the IPH need to state "A TAA straight-in, left base, or
right base area is the regulatory equivalent of a published approach
segment." Otherwise, the uncertainty and sharpshooting is endless. ;-)


Yep. And given the scanty training that controllers receive (or so I have
been told in these groups) WRT RNAV approaches, pilots had best make sure
that they and ATC have the same thing in mind when flying such a clearance.

--
Dan
T-182T at BFM


  #6  
Old October 10th 07, 03:03 PM posted to rec.aviation.ifr
Steven P. McNicoll
external usenet poster
 
Posts: 1,477
Default When to descend


"Bee" wrote in message
...

I guess the AIM and the IPH need to state "A TAA straight-in, left base,
or right base area is the regulatory equivalent of a published approach
segment." Otherwise, the uncertainty and sharpshooting is endless. ;-)


The AIM already states that, in the Pilot/Controller Glossary:


AREA NAVIGATION (RNAV) APPROACH CONFIGURATION:

a. STANDARD T- An RNAV approach whose design allows direct flight to
any one of three initial approach fixes (IAF) and eliminates the need for
procedure turns. The standard design is to align the procedure on the
extended centerline with the missed approach point (MAP) at the runway
threshold, the final approach fix (FAF), and the initial
approach/intermediate fix (IAF/IF). The other two IAFs will be established
perpendicular to the IF.

b. MODIFIED T- An RNAV approach design for single or multiple runways
where terrain or operational constraints do not allow for the standard T.
The "T" may be modified by increasing or decreasing the angle from the
corner IAF(s) to the IF or by eliminating one or both corner IAFs.

c. STANDARD I- An RNAV approach design for a single runway with both
corner IAFs eliminated. Course reversal or radar vectoring may be required
at busy terminals with multiple runways.

d. TERMINAL ARRIVAL AREA (TAA)- The TAA is controlled airspace
established in conjunction with the Standard or Modified T and I RNAV
approach configurations. In the standard TAA, there are three areas:
straight-in, left base, and right base. The arc boundaries of the three
areas of the TAA are published portions of the approach and allow aircraft
to transition from the en route structure direct to the nearest IAF. TAAs
will also eliminate or reduce feeder routes, departure extensions, and
procedure turns or course reversal.

1. STRAIGHT-IN AREA- A 30NM arc centered on the IF bounded by a
straight line extending through the IF perpendicular to the intermediate
course.

2. LEFT BASE AREA- A 30NM arc centered on the right corner IAF.
The area shares a boundary with the straight-in area except that it extends
out for 30NM from the IAF and is bounded on the other side by a line
extending from the IF through the FAF to the arc.

3. RIGHT BASE AREA- A 30NM arc centered on the left corner IAF.
The area shares a boundary with the straight-in area except that it extends
out for 30NM from the IAF and is bounded on the other side by a line
extending from the IF through the FAF to the arc.


  #7  
Old October 10th 07, 05:24 PM posted to rec.aviation.ifr
Steven P. McNicoll
external usenet poster
 
Posts: 1,477
Default When to descend


"Steven P. McNicoll" wrote in message
...

"Bee" wrote in message
...

I guess the AIM and the IPH need to state "A TAA straight-in, left base,
or right base area is the regulatory equivalent of a published approach
segment." Otherwise, the uncertainty and sharpshooting is endless. ;-)


The AIM already states that, in the Pilot/Controller Glossary:


AREA NAVIGATION (RNAV) APPROACH CONFIGURATION:

a. STANDARD T- An RNAV approach whose design allows direct flight to
any one of three initial approach fixes (IAF) and eliminates the need for
procedure turns. The standard design is to align the procedure on the
extended centerline with the missed approach point (MAP) at the runway
threshold, the final approach fix (FAF), and the initial
approach/intermediate fix (IAF/IF). The other two IAFs will be established
perpendicular to the IF.

b. MODIFIED T- An RNAV approach design for single or multiple runways
where terrain or operational constraints do not allow for the standard T.
The "T" may be modified by increasing or decreasing the angle from the
corner IAF(s) to the IF or by eliminating one or both corner IAFs.

c. STANDARD I- An RNAV approach design for a single runway with both
corner IAFs eliminated. Course reversal or radar vectoring may be required
at busy terminals with multiple runways.

d. TERMINAL ARRIVAL AREA (TAA)- The TAA is controlled airspace
established in conjunction with the Standard or Modified T and I RNAV
approach configurations. In the standard TAA, there are three areas:
straight-in, left base, and right base. The arc boundaries of the three
areas of the TAA are published portions of the approach and allow aircraft
to transition from the en route structure direct to the nearest IAF. TAAs
will also eliminate or reduce feeder routes, departure extensions, and
procedure turns or course reversal.

1. STRAIGHT-IN AREA- A 30NM arc centered on the IF bounded by a
straight line extending through the IF perpendicular to the intermediate
course.

2. LEFT BASE AREA- A 30NM arc centered on the right corner IAF.
The area shares a boundary with the straight-in area except that it
extends out for 30NM from the IAF and is bounded on the other side by a
line extending from the IF through the FAF to the arc.

3. RIGHT BASE AREA- A 30NM arc centered on the left corner IAF.
The area shares a boundary with the straight-in area except that it
extends out for 30NM from the IAF and is bounded on the other side by a
line extending from the IF through the FAF to the arc.


The Instrument Flying Handbook, dated 2001, also states, "The arc boundaries
of the three areas of the TAA are published portions of the approach and
allow aircraft to transition from the en route structure direct to the
nearest IAF." Apparently pilots are not making an effort to keep current on
procedures.


  #8  
Old October 10th 07, 06:18 PM posted to rec.aviation.ifr
Ron Rosenfeld
external usenet poster
 
Posts: 264
Default When to descend

On Tue, 09 Oct 2007 18:14:12 -0700, Bee wrote:

I guess the AIM and the IPH need to state "A TAA straight-in, left base,
or right base area is the regulatory equivalent of a published approach


It's in the PC/G:

TERMINAL ARRIVAL AREA (TAA)- The TAA is controlled airspace established in
conjunction with the Standard or Modified T and I RNAV approach
configurations. In the standard TAA, there are three areas: straight-in,
left base, and right base. The arc boundaries of the three areas of the TAA
**are published portions of the approach** and allow aircraft to transition
from the en route structure direct to the nearest IAF. TAAs will also
eliminate or reduce feeder routes, departure extensions, and procedure
turns or course reversal.

(emphasis mine)
Ron (EPM) (N5843Q, Mooney M20E) (CP, ASEL, ASES, IA)
  #9  
Old October 11th 07, 02:26 AM posted to rec.aviation.ifr
Bee
external usenet poster
 
Posts: 29
Default When to descend

Ron Rosenfeld wrote:

On Tue, 09 Oct 2007 18:14:12 -0700, Bee wrote:


I guess the AIM and the IPH need to state "A TAA straight-in, left base,
or right base area is the regulatory equivalent of a published approach



It's in the PC/G:

TERMINAL ARRIVAL AREA (TAA)- The TAA is controlled airspace established in
conjunction with the Standard or Modified T and I RNAV approach
configurations. In the standard TAA, there are three areas: straight-in,
left base, and right base. The arc boundaries of the three areas of the TAA
**are published portions of the approach** and allow aircraft to transition
from the en route structure direct to the nearest IAF. TAAs will also
eliminate or reduce feeder routes, departure extensions, and procedure
turns or course reversal.

(emphasis mine)
Ron (EPM) (N5843Q, Mooney M20E) (CP, ASEL, ASES, IA)


Great cite. Too bad most of the folks here cannot figure out how to
find this stuff.
  #10  
Old October 11th 07, 02:23 PM posted to rec.aviation.ifr
Dave Butler
external usenet poster
 
Posts: 147
Default When to descend

Bee wrote:

Great cite. Too bad most of the folks here cannot figure out how to
find this stuff.


Great cite of a pretty good site.

True enough, but if everyone just looked everything up and found the
answers and interpreted everything correctly, we wouldn't have much to
talk about here.

Anyway, I certainly wouldn't fault the OP for raising the question here.
It provoked an interesting discussion and I learned from it.

Dave
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 08:55 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright ©2004-2025 AviationBanter.
The comments are property of their posters.