 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Dispatcher is informed that one of his ETOPS flights is being flown by a non ETOPS aircraft. The flight is past the midpoint and continues to destination.
| Attributes | |
| ACN | 1291803 |
| Time | |
| Date | 201508 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | Large Transport |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Takeoff |
| Route In Use | Oceanic |
| Flight Plan | IFR |
| Person 1 | |
| Function | Dispatcher |
| Qualification | Dispatch Dispatcher |
| Events | |
| Anomaly | Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
Narrative:
Dispatcher was notified that one of his flights was a non-ETOPS aircraft flying ETOPS; about two hours prior to arrival. Flight was past his equal time point (etp) and continued to destination. Captain was contacted and made aware of the situation.aircraft was routed on an ETOPS routing; passed its ETOPS inspection and had a logbook that stated ETOPS across the front of it. Flight was dispatched on an ETOPS flight without any computer checks that should have caught it. Extenuating circumstances include workload and weather/ATC restrictions involving a hurricane enroute. Bottom line was human error in this case. This incident occurred due to a string of errors that should have been caught. Maintenance control routing restrictions; captain or dispatcher diligence and computer programing errors all contributed to this incident.
Original NASA ASRS Text
Title: Dispatcher is informed that one of his ETOPS flights is being flown by a non ETOPS aircraft. The Flight is past the midpoint and continues to destination.
Narrative: Dispatcher was notified that one of his flights was a non-ETOPS aircraft flying ETOPS; about two hours prior to arrival. Flight was past his Equal Time Point (ETP) and continued to destination. Captain was contacted and made aware of the situation.Aircraft was routed on an ETOPS routing; passed its ETOPS inspection and had a logbook that stated ETOPS across the front of it. Flight was dispatched on an ETOPS flight without any computer checks that should have caught it. Extenuating circumstances include workload and weather/ATC restrictions involving a hurricane enroute. Bottom line was human error in this case. This incident occurred due to a string of errors that should have been caught. Maintenance Control routing restrictions; Captain or Dispatcher diligence and computer programing errors all contributed to this incident.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.