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

LDA/Glide Slope Approach: Precision?

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
Check rides

both 121.441 and 135.297 require pilots to demonstrate proficiency in all precision approaches the company uses on every Proficiency Check. If the LDA/w GS was a precision approach every company pilot would have to shoot one every check ride along with the ILS and PAR if authorized by the op specs. We do not demonstrate proficiency in the LDA because it is a NPA.
 
Neither Part 121 nor Part 135 require that a pilot demonstrate all precision approaches authorized on every checkride. During a proficiency check, a pilot in command must execute at least one normal ILS approach, and one with a simulated engine failure. The pilot must also execute a non-precison approach.

You refer to 121.441, which uses Appendix F of Part 121 as the guide, the relevant portion copied below. In no way does it state that every precision approach must be executed, for which an operator is authorized. Regardless, this does not define the nature of a precision approach. The definition of a precision approach is specified in the opening part to 14 CFR.

A precision approach is clearly defined as one having vertical guidance, while a non precision approach is clearly defined as one that does not have vertical guidance, as previously given. How much more clear can this be?

Part 121, Appendix F, subparagraph (c):

(c) ILS and other instrument approaches. There must be the following:

(1) At least one normal ILS approach.

(2) At least one manually controlled ILS approach with a simulated failure of one powerplant. The simulated failure should occur before initiating the final approach course and must continue to touchdown or through the missed approach procedure.

(3) At least one nonprecision approach procedure that is representative of the nonprecision approach procedures that the certificate holder is likely to use.

(4) Demonstration of at least one nonprecision approach procedure on a letdown aid other than the approach procedure performed under subparagraph (3) of this paragraph that the certificate holder is approved to use. If performed in a training device, the procedures must be observed by a check pilot or an approved instructor.

Each instrument approach must be performed according to any procedures and limitations approved for the approach facility used. The instrument approach begins when the airplane is over the initial approach fix for the approach procedure being used (or turned over to the final approach controller in the case of CA approach) and ends when the airplane touches down on the runway or when transition to a missed approach configuration is completed. Instrument conditions need not be simulated below 100 feet above touchdown zone elevation.

Regarding 135.297, it would appear you alluded to subparagraph (b), which states:

"(b) No pilot may use any type of precision instrument approach procedure under IFR unless, since the beginning of the 6th calendar month before that use, the pilot satisfactorily demonstrated that type of approach procedure. No pilot may use any type of nonprecision approach procedure under IFR unless, since the beginning of the 6th calendar month before that use, the pilot has satisfactorily demonstrated either that type of approach procedure or any other two different types of nonprecision approach procedures. The instrument approach procedure or procedures must include at least one straight-in approach, one circling approach, and one missed approach. Each type of approach procedure demonstrated must be conducted to published minimums for that procedure."

This is not to be construed as meaning that a pilot must demonstrate every approach authorized that operator. However, if a pilot wishes to execute a precision proceedure that is authorized to that operator, then he or she must have demonstrated it within the preceeding six callendar months.

As we discussed by PM, your ops specs do not place an LDA with a glide sloope under the heading of non-precison, as this was changed two years ago to a heading describing approaches other than an ILS, MLS, GLS, etc. This is an important distinction, and it was made with the intent of recognizing the upcoming of other types of precision approaches, or approaches which are not nonprecision.
 
135.297 (b)

135.297 (b) No pilot may use any type of precision instrument approach procedure under IFR unless, since the beginning of the 6th calendar month before that use, the pilot satisfactorily demonstrated that type of approach. got to on 135.
 
Must shoot the PA

That is what I said, you said I did not have to shoot every PA in my op specs, my POI says we must demonstrate proficieny in every PA in our Op specs. she and her FSDO call the LDA/w GS a NPA.
 
No, Pilotyip, this is not correct. You do not have the power or authority to interpret the FAR; neither does your POI, or anybody at the FSDO level.

You are NOT required to demonstrate every approved precision approach in your opspecs. You may not fly an approach you have not demonstrated in the previous 6 months, but nowhere under Part 135 are you required to fly every approach. If you don't demonstrate each precision approach, you may not fly it, but there is NO requirement to demonstrate it, or to later fly it. If you don't demonstrate it, you're simply restricted from flying it.

Do you demonstrate a MLS approach every 6 months?

Part 121 doesn't require even this; only the three approaches as given in my previous post, and quoted from Appendix F.

The CFR, however, is legal evidence of itself, as a codification that stands alone without specific constitutional reference or enpowerment. Being self-evidentiary, the provision of definition set forth in 14 CFR 1.1 is ample description and conclusion as to the nature of an approach that includes vertical guidance.

What does that all boil down to? Your OpSpecs don't define the FAR, or the terms set forth in the FAR. Your POI doesn't have the ability to do so, either. Neither does a soul at your FSDO. The power and authority to do so is not granted at that level.

Any classification in your OpSpecs does not define the FAR, nor does it define TERPS. The OpSpecs do not clarify or represent the FAR, nor may they be used as evidence to interpret the FAR. How should one view an approach if one does not work for a certificate holder, and has no OpSpecs? Would your OpSpecs be applicable to such a person? Of course not. However, 14 CFR 1.1 would be, and is.
 
MLS

can not do MLS or PAR or ASR, not in our ops specs, you are telling me a FSDO can not define how it views the regs? An LDA with gs is a NPA
 
Avbug,

This is a bit off the original subject, but since it came up I have a question. You stated that "Opspecs don't define the FAR" and "do not clarify or represent the FAR" but 121.625 Alternate airport weather minimums states in part that, " weather conditions will be at or above the alternate weather minimums specified in the certificate holder's operations specifications".

Isn't this an example of Opspecs defining an FAR?

Because my Opspecs define LDA w or w/o GS as nonprecision then for me, and everyone at my company, it is nonprecision.

The LDA issue is a matter of semantics. What difference does it make what you call it as long as you know how to fly it and how to make decisions based on your understanding of the approach.

My.02
 
When the OPSS provides information or direction to an operator, it is binding to that operator, only. Takeoff minimums and alternate minimums may vary, according to the pilot qualifications and experience, as well as the operator limitations. This doesn't redefine the FAR, but only provides on an individual basis the limitations for a given operator or pilot. This is the purpose of OPSS, or OpSpecs.

OpSpecs are approved data, meaning data approved by the administrator for a particular purpose In this case, for a particular operator, and a finite group of pilots. OpSpecs do not define the FAR.

As for inspector opinions and the FSDO...yes, I mean exactly what I said. The FSDO does NOT have the right or authority to interpret regulation or to issue interpretations. The FSDO has the authority to initiate enforcement action (but not to follow through or complete that action).

Does your OPSpec C052 classify an LDA w/gs as nonprecision, or does it classify it under "Instrument Approach Procedures Other Than ILS, MLS, and GLS?" It should include in parenthesis "(eg, nonprecision approaches)." This change was made two years ago, and has been referred to several times here.

According to HBAT 99-17, "C. The general classification of "nonprecision" was replaced in order to recognize current and future authorizations for RNAV and other approaches that may incorporate the use of barometric VNAV to provide a stabilized descent."

Be that as it may, the OPSS doesn't define the FAR. What may be for you, or for your company, is not for everybody. The OpSpec doesn't represent an interpretation, but a set or restrictions and limitations applicable only to the user. Any classifications therein are not evidence of the FAR, and OpSpecs can't b used to define TERPS or Part 97 of 14 CFR.
 

Latest resources

Back
Top