Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

Misunderstanding 91.175

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web

Pilot12345

Member
Joined
Oct 24, 2004
Posts
20
After reading this article I wanted to get some other opinions on it. I have never heard of a "green terminating bar" only "red". Can someone explain? Is there a mistake in 91.175? Thanks!

Misunderstanding Part 91.175
by Cody Johnson
Reprinted with permission from FAA Aviation News
part91.jpg
An aircraft crashed several months ago while executing a locator/distance measuring equipment (LOC/DME) approach. The aircraft descended to the minimum descent altitude (MDA) then purportedly the pilot reported on the Cockpit Voice Recorder (CVR) that he “had the approach lights.” The aircraft continued a descent below the MDA and struck a rising tree-covered hill a few miles from the end of the runway.
In the course of the investigation, the National Transportation Safety Board (NTSB) began evaluating Title 14 of the Code of Federal Regulations (14 CFR) Section 91.175(c), “Takeoff and Landing under IFR.” They have asked the FAA to explain why the rule has, what they believe, an unsafe provision. Specifically, the rule states that once a pilot, who is established at MDA, sees the approach lights he can descend below the MDA to 100 feet above the touchdown zone elevation (TDZE):
This would lead one to believe that a pilot could descend below the MDA several miles from the end of the runway based on the fact that he saw some approach lights in a low visibility situation (night/IFR/rain). That in fact is not the intent of the rule. The rule contains many provisions and extensive criteria born over years of experience and accidents.
For example, the 100-foot restriction only applies when using the approach lighting system. The reason is simply that the approach lighting system isn’t the runway; it’s the environment prior to reaching the runway. You need something else that will verify positive contact and let you know where the end of the runway is. If you are only using the approach lighting system and don’t have the runway environment itself in sight, you need either the red terminating bars or the red side row bars to go below 100 feet above the TDZE.

If you have any of the other elements indicated in 14 CFR 91.175(c)(3), you do not have this restriction. Again, the aim of this regulation is to require you to have positive contact with the runway and to be able to identify the threshold. If you can see the threshold lights, touchdown zone lights, runway lights, etc., then you are seeing something that is beyond the threshold. If you are looking only at approach lights, you have no exact idea of where the runway actually begins, hence the requirement.

If you have the threshold, threshold markings, threshold lights, runway and identification lights (REIL), visual approach slope indicator (VASI), touchdown zone (TDZ) or TDZ markings, TDZ lights, runway or runway markings, or the runway lights, you are not restricted to the 100-foot limitation.

If you reach decision height (DH) or the applicable MDA and have the approach lights in sight, you may continue on your descent, using those lights until reaching 100 feet above the TDZ elevation. At that point, if you do not have the requisite red terminating bars or side row bars, you are obligated to perform a missed approach. However, if when arriving at 100 feet you have other elements visible as described above, then you may continue, as you are no longer using only the approach lighting system. The restriction applies when using the approach lighting system only, for your visual reference. It’s important to have this provision for those non-precision approaches (VOR/ADF) with relatively high MDAs (500-700’ height above touchdown or HAT) so a pilot has a reasonable chance of complying with Section 91.175(c)(1).

Also applicable to this question is the very important issue of what approach lighting systems (ALS) use, red terminating bars or side row bars. You need this information when planning the approach, and it is provided with the approach chart. The ALSF-1 (with sequenced flashing lights) provides red terminating bars, and the ALSF-II provides side row bars. The runway in question in this accident is equipped with a Medium Intensity Approach Light System (MALS), which contains a green terminating bar and a sequenced flasher—no red lights!

Section 91.129(e)(3), Operations in Class D Airspace, is also extremely applicable in this accident. It says, “An airplane approaching to land on a runway served by a visual approach slope indicator shall maintain an altitude at or above the glide slope until a lower altitude is necessary for safe landing.”

If the pilot followed this rule he would be alive today. Runway 36 at Kirksville is equipped with a VASI. Whether it was working, or working properly, is a job for the investigators. But Section 91.175 was not the basis for this accident.
 
If you have the threshold lights (which are green) in sight you can land.

But unless I'm mistaken you are responsible for your own obstacle clearance once you dip below the glideslope.
 
Well I meant that if you are on the glide slope, or above the MDA between the FAF (or last stepdown fix) and the MAP, you're assured obstacle clerance.

I figg'rd that's what ya meant...just bustin balls since my Indians are done and my Browns...well, they never got started this year.

-mini
 
But unless I'm mistaken you are responsible for your own obstacle clearance once you dip below the glideslope.

Why would you go below glideslope? There is no reason to go below glideslope. Most company manuals prohibit intentional flight below glideslope except during visual approaches and then only when required.
 
Why would you go below glideslope? There is no reason to go below glideslope. Most company manuals prohibit intentional flight below glideslope except during visual approaches and then only when required.
So you don't waste 1,000 feet of runway.

And if you want to be picky about it, the glide slope isn't necessarily reliable beyond the DH (assuming there is a DH)

That being said, if I’m flying for a company that says don’t go below the glide path unless it’s necessary, than I won’t.
 
Why would you go below glideslope? There is no reason to go below glideslope.
Because in the daytime, I can see the ground that I'm not going to fly into. Glideslope guidance is an aid. Most days, I don't need an aid, so I'll aim at the threshold and buy myself more concrete for the landing roll.
However, you are correct: many companies do not allow it. Mine does.
 
So you don't waste 1,000 feet of runway.

And if you want to be picky about it, the glide slope isn't necessarily reliable beyond the DH (assuming there is a DH)

That being said, if I’m flying for a company that says don’t go below the glide path unless it’s necessary, than I won’t.

We had a guy who didnt want to waste 1000 feet of runway, and he paid for it with his life. Flying a Navajo into SDF at night during the big jets cargo meet, you have to stay a dot or so HIGH otherwise you are in the wake.

The only time i stay right on the glideslope is if im going down to absolute minimums and there hasnt been any heavy jet activity ahead of me, otherwise im slightly above it.
 
Last edited:

Latest resources

Back
Top