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

Say Again #51



 
 
Thread Tools Display Modes
  #1  
Old June 25th 05, 02:48 PM
Paul Lynch
external usenet poster
 
Posts: n/a
Default

Don't forget, the AIM is not regulatory. It is an informational source.
You can't violate it. You can violate 91.185.

The military taught me (and they generally teach exactly what is in the FARs
with some exceptions) to fly as the AIM says. They still teach that (See
USAF instrument flight procedures manual; its online). You commence your
approach at your ETA, hold if you are early. Practically, unless you got
there very early, you commence the approach (any one you want). ATC will
clear the airspace. You have to trust the controllers to do their job just
like they are trusting you will do yours and follow the published guidance
in the FARs (excuse me 14 CFR 91, the aquisition folks trademarked "FAR")

wrote in message
oups.com...

I was just reading Don Brown's latest (6/22) on avweb:
http://www.avweb.com/news/columns/189944-1.html

This column is about NORDO IFR procedures. I like Don's columns and
find their nitpickiness to be consistent with safe flying, if a little
bit annoying.

But in this column, two things stuck out at me as odd.

First:

Flight plan was: HKY..BZM.V20.SUG.V185.SOT.V136.VXV..TYS
VXV is an IAF for TYS.

Don's interpretation of the AIM is that since the pilot was almost
certainly cleared to TYS, then that's his clearance limit. The regs say
fly to your clearance limit, and initiate your approach at the ETA.
That means a pilot would fly to VXV (his IAF), fly to the airport (?!),
fly back to VXV, then do full approach.

It seems a tad ridiculous, no?


Second:

Descent. We all know the rules about staying at the highest of our
last clearance, the MEA, or an altitude given in an EFC. If we filed
for 15000 and the airport is at, say, sea level, there's a lot of
altitude to lose. When and where is the right time to do this? I'm
embarassed to say I never really thought about it much before. Usually,
controllers descend us gradually. Or if we're VFR we descend ourselves
gradually. But the rules make it clear you're to keep the altitude up
until ... when? When you start the approach? Come down in a hold?
where?

He bring's this up also questioning this, and mentioning the AIM
paragraph that says these proecedures don't always fit; use your own
judgement, etc.

Still, I'd like to know what I was going to do in this situation. What
would you do?

-- dave j
-- jacobowitz73 --at-- yahoo --dot-- com



  #2  
Old June 25th 05, 03:19 PM
external usenet poster
 
Posts: n/a
Default



Paul Lynch wrote:

Don't forget, the AIM is not regulatory. It is an informational source.
You can't violate it. You can violate 91.185.


That isn't quite correct. Some of the information in the AIM is informational.
But, some of it is directive and expands upon regulatory requirements. There
have been many enforcement actions under FAR 91.13 for failure to adhere to
directive language in the AIM.

The introduction to the AIM reads:

"This manual is designed to provide the aviation community with basic flight
information and ATC procedures for use in the National Airspace System (NAS) of
the United States. An international version called the Aeronautical Information
Publication contains parallel information, as well as specific information on
the international airports for use by the international community.

This manual contains the fundamentals required in order to fly in the United
States NAS. It also contains items of interest to pilots concerning health and
medical facts, factors affecting flight safety, a pilot/controller glossary of
terms used in the ATC System, and information on safety, accident, and hazard
reporting."

Note the second paragraph about "required fundamentals" and also "items of
interest."

An example is the additional reporting requirements listed in the AIM:

"5-3-3. Additional Reports
a. The following reports should be made to ATC or FSS facilities without a
specific ATC request:
1. At all times.
(a) When vacating any previously assigned altitude or flight level for a newly
assigned altitude or flight level.
(b) When an altitude change will be made if operating on a clearance specifying
VFR-on-top.
(c) When unable to climb/descend at a rate of a least 500 feet per minute.
(d) When approach has been missed. (Request clearance for specific action; i.e.,
to alternative airport, another approach, etc.)
(e) Change in the average true airspeed (at cruising altitude) when it varies by
5 percent or 10 knots (whichever is greater) from that filed in the flight plan.

(f) The time and altitude or flight level upon reaching a holding fix or point
to which cleared.
(g) When leaving any assigned holding fix or point."

Failure to make one of those reports has resulted in enforcement proceedings
under 91.13 and 91.183 (c) many times over the years. The fact that 5-3-3 a
says "should" is only because the FAA legal folks have consistently held that
use of the word "shall" for such passages in the AIM would constitute
rule-making, per se. Then, they would have to run every change to the AIM
through the complete NPRM process. No country does that under the ICAO rules
for its AIP (which the AIM is a domestic version of the United State's AIP.

"Should" works with the effect of regulation when coupled (in this case) with
91.183 (c), which is in accordance with ICAO international conventions.

  #3  
Old June 25th 05, 03:58 PM
Jim Baker
external usenet poster
 
Posts: n/a
Default


wrote in message ...


Paul Lynch wrote:

Don't forget, the AIM is not regulatory. It is an informational source.
You can't violate it. You can violate 91.185.


That isn't quite correct. Some of the information in the AIM is
informational.
But, some of it is directive and expands upon regulatory requirements.
There
have been many enforcement actions under FAR 91.13 for failure to adhere
to
directive language in the AIM.

The introduction to the AIM reads:

"This manual is designed to provide the aviation community with basic
flight
information and ATC procedures for use in the National Airspace System
(NAS) of
the United States. An international version called the Aeronautical
Information
Publication contains parallel information, as well as specific information
on
the international airports for use by the international community.

This manual contains the fundamentals required in order to fly in the
United
States NAS. It also contains items of interest to pilots concerning health
and
medical facts, factors affecting flight safety, a pilot/controller
glossary of
terms used in the ATC System, and information on safety, accident, and
hazard
reporting."

Note the second paragraph about "required fundamentals" and also "items of
interest."

An example is the additional reporting requirements listed in the AIM:

"5-3-3. Additional Reports
a. The following reports should be made to ATC or FSS facilities without a
specific ATC request:
1. At all times.
(a) When vacating any previously assigned altitude or flight level for a
newly
assigned altitude or flight level.
(b) When an altitude change will be made if operating on a clearance
specifying
VFR-on-top.
(c) When unable to climb/descend at a rate of a least 500 feet per minute.
(d) When approach has been missed. (Request clearance for specific action;
i.e.,
to alternative airport, another approach, etc.)
(e) Change in the average true airspeed (at cruising altitude) when it
varies by
5 percent or 10 knots (whichever is greater) from that filed in the flight
plan.
(f) The time and altitude or flight level upon reaching a holding fix or
point
to which cleared.
(g) When leaving any assigned holding fix or point."

Failure to make one of those reports has resulted in enforcement
proceedings
under 91.13 and 91.183 (c) many times over the years. The fact that 5-3-3
a
says "should" is only because the FAA legal folks have consistently held
that
use of the word "shall" for such passages in the AIM would constitute
rule-making, per se. Then, they would have to run every change to the AIM
through the complete NPRM process. No country does that under the ICAO
rules
for its AIP (which the AIM is a domestic version of the United State's
AIP.

"Should" works with the effect of regulation when coupled (in this case)
with
91.183 (c), which is in accordance with ICAO international conventions.


Wow, Tim, you're going to open a huge can of worms with that!! LOL. About 2
to 3 years ago I wrote practically the same thing regarding 5-3-3 and got in
a big thread with the inhabitants here, especially Newps, about it. The
thread began with whether you should make a report when vacating a
previously assigned altitude or flight level. The controllers and many
other pilots contended, this from memory, that it wasn't required and
garbaged up the freq. I cited 5-3-3, the "should" and "at all times"
language, and rec'd a barrage of return fire. In particular, when I played
devils advocate and told Newps and the other naysayers I must not be
required then to make any of the other reports therein, since I didn't have
to make 5-3-3, 1, (a), and could apply their logic to the rest of the para,
I was castigated for trolling, IIRC, LOL. I stopped, but about 3 months
later rec'd an email from Don Brown, who had read the thread. He agreed
with my position and the others in the thread who read 5-3-3 as I did.

My point in that thread, and this, is to wonder why any pilot would stake
his ticket, his life, or others lives on the opinions of controllers or
anyone else who advocated not adhering to procedure for convenience sake.
Jose, above, said he'd stake his ticket on it. I don't know him, am sure
he's an upstanding citizen etc., but think that's a very foolhardy and
dangerous attitude/opinion. I wonder about a pilot who is skilled enough to
fly IMC in the NAS yet considers the loss of a radio an emergency (assuming
of course that nothing else is wrong). The aircraft is still flying,
there's procedure to keep him and all around him safe, and he doesn't have
the distraction of someone talking in his ear telling him what to do. I
just don't see that angle as being justification to make up your own game
plan, in IMC, and hope that someone on the ground is going to defend you
when theres an inquiry. If I was doing the investigation, I'd have to ask
the guy why he thought he was in an emergency situation and the answer had
better contain more failures than just a radio.

Anyway, in a time far far away, that's what they taught me at the SAC
Instrument Flight Course, to say nothing of UPT and the annual required
instrument refresher courses we had to endure in the USAF.

Jim


  #4  
Old June 25th 05, 07:30 PM
external usenet poster
 
Posts: n/a
Default



Jim Baker wrote:

Wow, Tim, you're going to open a huge can of worms with that!! LOL. About 2
to 3 years ago I wrote practically the same thing regarding 5-3-3 and got in
a big thread with the inhabitants here, especially Newps, about it. The
thread began with whether you should make a report when vacating a
previously assigned altitude or flight level. The controllers and many
other pilots contended, this from memory, that it wasn't required and
garbaged up the freq. I cited 5-3-3, the "should" and "at all times"
language, and rec'd a barrage of return fire.


Those who scoff at this stuff haven't been involved in rule-making or the
enforcement posture of the FAA. Because the FAA does not invoke enforcement for
things like these comm reports unless something really goes wrong, it becomes
easy to think they are optional.

Failure to report a previously assigned altitude in a radar environment would
almost certainly never result in an enforcement proceeding. Failure to make the
same report in a non-radar environment increases the chances of being sanctioned
to some degree.

I know, I have been through this stuff here before and am immune to those who
say "BS." ;-) I brought it up this time in the spirit of how I would include it
in a ground school course. In a training context, I would place it far below
the knowledge needed to survive in the system. But, neglecting to teach the
legal nuances of this "lesser" stuff is inappropriate.

  #5  
Old June 25th 05, 08:02 PM
Jose
external usenet poster
 
Posts: n/a
Default

My point in that thread, and this, is to wonder why any pilot would stake
his ticket, his life, or others lives on the opinions of controllers or
anyone else who advocated not adhering to procedure for convenience sake.
Jose, above, said he'd stake his ticket on it.


I did not say that. What I said was that I would do so in the case of
an =emergency=, not for the sake of =convenience=. And I also said that
in the context of "to the extent necessary to meet the emergency". Lost
comm under VFR is inconvenient. Lost comm under IFR can be an
emergency, depending on circumstances.

The aircraft is still flying,
there's procedure to keep him and all around him safe, and he doesn't have
the distraction of someone talking in his ear telling him what to do.


That procedure may work in the midwest, where there's not so much
traffic, but in the Northeast, especially if my transponder has also
gone to lunch, that procedure may =not= actually keep me safe. I would
make a judgement call based on circumstances. I would expect the FAA to
back me if some controller got a bug up his posterior.

Jose
--
You may not get what you pay for, but you sure as hell pay for what you get.
for Email, make the obvious change in the address.
  #6  
Old June 26th 05, 07:45 PM
Bob Gardner
external usenet poster
 
Posts: n/a
Default

Mary Yodice, writing a legal column in either the AOPA Pilot or Flight
Training, I can't remember which, warned pilots that relying on the
non-regulatory status of the AIM was a mistake. An NTSB administrative law
judge gets to decide if a particular action or fail to act constitutes
"careless and reckless," and failing to use the guidance in the AIM puts you
right in their crosshairs.

Bob Gardner

"Paul Lynch" wrote in message
news:vgdve.27603$%Z2.20038@lakeread08...
Don't forget, the AIM is not regulatory. It is an informational source.
You can't violate it. You can violate 91.185.

The military taught me (and they generally teach exactly what is in the
FARs with some exceptions) to fly as the AIM says. They still teach that
(See USAF instrument flight procedures manual; its online). You commence
your approach at your ETA, hold if you are early. Practically, unless you
got there very early, you commence the approach (any one you want). ATC
will clear the airspace. You have to trust the controllers to do their
job just like they are trusting you will do yours and follow the published
guidance in the FARs (excuse me 14 CFR 91, the aquisition folks
trademarked "FAR")

wrote in message
oups.com...

I was just reading Don Brown's latest (6/22) on avweb:
http://www.avweb.com/news/columns/189944-1.html

This column is about NORDO IFR procedures. I like Don's columns and
find their nitpickiness to be consistent with safe flying, if a little
bit annoying.

But in this column, two things stuck out at me as odd.

First:

Flight plan was: HKY..BZM.V20.SUG.V185.SOT.V136.VXV..TYS
VXV is an IAF for TYS.

Don's interpretation of the AIM is that since the pilot was almost
certainly cleared to TYS, then that's his clearance limit. The regs say
fly to your clearance limit, and initiate your approach at the ETA.
That means a pilot would fly to VXV (his IAF), fly to the airport (?!),
fly back to VXV, then do full approach.

It seems a tad ridiculous, no?


Second:

Descent. We all know the rules about staying at the highest of our
last clearance, the MEA, or an altitude given in an EFC. If we filed
for 15000 and the airport is at, say, sea level, there's a lot of
altitude to lose. When and where is the right time to do this? I'm
embarassed to say I never really thought about it much before. Usually,
controllers descend us gradually. Or if we're VFR we descend ourselves
gradually. But the rules make it clear you're to keep the altitude up
until ... when? When you start the approach? Come down in a hold?
where?

He bring's this up also questioning this, and mentioning the AIM
paragraph that says these proecedures don't always fit; use your own
judgement, etc.

Still, I'd like to know what I was going to do in this situation. What
would you do?

-- dave j
-- jacobowitz73 --at-- yahoo --dot-- com





  #7  
Old June 26th 05, 10:04 PM
G. Sylvester
external usenet poster
 
Posts: n/a
Default

Bob Gardner wrote:
Mary Yodice, writing a legal column in either the AOPA Pilot or Flight
Training, I can't remember which, warned pilots that relying on the
non-regulatory status of the AIM was a mistake. An NTSB administrative law
judge gets to decide if a particular action or fail to act constitutes
"careless and reckless," and failing to use the guidance in the AIM puts you
right in their crosshairs.
Bob Gardner



Bob, thanks for the reference. It took a little while but here's the
link.

http://www.aopa.org/members/ftmag/ar...m?article=4421

So basically the AIM is non-regulatory but following those
'mere suggestions' is a good idea as they might come back
to haunt you in the worst of times.

thanks.

Gerald Sylvester
 




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 02:46 PM.


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