Are misleading information events reportable if they occur without flight deck alerts?

Yes, misleading information without flight deck alerts should be included in a reportable event.

What is the regulatory basis for AMC3 ORO.GEN.160?

The regulatory basis is ED Decision 2022/012/R.

AMC3 ORO.GEN.160 Occurrence reporting

Q: What should be included in a reportable event according to AMC3 ORO.GEN.160?

A reportable event should include: significant deviations from the flight path not caused by flight crew input; misleading information without flight deck alerts; loss of airborne navigation equipment functions necessary for the operation; loss of functions or facilities at the aerodrome necessary for the operation, including aerodrome operating procedures, ATC operation, navigation facilities, visual aids and electrical power supply; loss of other functions related to external infrastructure necessary for the operation; and any other event causing the approach or landing to be abandoned if occurring repeatedly.

Q: Which events related to flight path deviations are considered reportable under AMC3 ORO.GEN.160?

Significant deviations from the flight path not caused by flight crew input are considered reportable.

Q: What types of loss of airborne navigation equipment functions are reportable?

Loss of airborne navigation equipment functions necessary for the operation is reportable.

Q: Which aerodrome-related losses are considered reportable events?

Loss of functions or facilities at the aerodrome necessary for the operation, including aerodrome operating procedures, ATC operation, navigation facilities, visual aids and electrical power supply, are reportable.

Q: Are losses of external infrastructure functions reportable?

Yes, loss of other functions related to external infrastructure necessary for the operation is reportable.

Q: When should an event causing the approach or landing to be abandoned be reported?

Any other event causing the approach or landing to be abandoned should be reported if it occurs repeatedly.

Q: To whom should reports be submitted according to AMC3 ORO.GEN.160?

Reports should be submitted to the aerodrome involved when relevant and in addition to the recipients prescribed in ORO.GEN.160(b).

Navigate / EASA

Ask question Discover more Add to collection

AMC3 ORO.GEN.160 Occurrence reporting

ED Decision 2022/012/R

REPORTABLE EVENTS OF LVOs

(a) A reportable event should include:

(1) significant deviations from the flight path not caused by flight crew input;

(2) misleading information without flight deck alerts;

(3) loss of airborne navigation equipment functions necessary for the operation;

(4) loss of functions or facilities at the aerodrome necessary for the operation, including aerodrome operating procedures, ATC operation, navigation facilities, visual aids and electrical power supply;

(5) loss of other functions related to external infrastructure necessary for the operation; and

(6) any other event causing the approach or landing to be abandoned if occurring repeatedly.

(b) The reports should be submitted to the aerodrome involved when relevant and in addition to the recipients prescribed in ORO.GEN.160(b).

Details

Source-Title: AMC3 ORO.GEN.160 Occurrence reporting View latest amendments

Erulesid: ERULES-1963177438-19631 Compare versions

Domain: Air operations

Applicabilitydate: 30 October, 2022

Entryintoforcedate: 1 July, 2022

Regulatorysource: ED Decision 2022/012/R Navigate

Regulatorysubject: Part-ORO

Typeofcontent: AMC to IR (Acceptable means of compliance to implementing rule)

Parentir: ORO.GEN.160 Occurrence reporting

Origin: EASA

Category: EAR