 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier dispatchers reported an illegal flight plan was generated that would have taken the aircraft into class ii airspace had the error not been caught in time.
| Attributes | |
| ACN | 1243715 |
| Time | |
| Date | 201502 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | MDPC.Airport |
| State Reference | FO |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Route In Use | Oceanic |
| Flight Plan | IFR |
| Person 1 | |
| Function | Dispatcher |
| Qualification | Dispatch Dispatcher |
| Person 2 | |
| Function | Dispatcher |
| Qualification | Dispatch Dispatcher |
| Events | |
| Anomaly | Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
Narrative:
PIC contacted dispatch via ACARS to query their filed flight plan. Crew began checking their route after departure and discovered that the flight had been inadvertently filed into oceanic (class ii) airspace. I assisted crew with a route out of the class ii airspace within their fuel onboard to allow continuation of the flight in accordance with far. Flight continued without further incident.upon further review; it appears as though the planning dispatcher attempted to utilize route optimization while planning and even though they had selected class I as the mission type (proper selection for the equipment type assigned to the flight); the flight planning software does not guard against planning that aircraft through class ii airspace even though class I was selected. The planning dispatcher appears to have failed to double-check the route for compliance with far and equipment capabilities. The error was not identified until after flight departure; but before entering class ii airspace.
Original NASA ASRS Text
Title: Air carrier dispatchers reported an illegal flight plan was generated that would have taken the aircraft into Class II airspace had the error not been caught in time.
Narrative: PIC contacted Dispatch via ACARS to query their filed flight plan. Crew began checking their route after departure and discovered that the flight had been inadvertently filed into Oceanic (Class II) Airspace. I assisted crew with a route out of the Class II airspace within their fuel onboard to allow continuation of the flight in accordance with FAR. Flight continued without further incident.Upon further review; it appears as though the planning Dispatcher attempted to utilize route optimization while planning and even though they had selected Class I as the mission type (proper selection for the equipment type assigned to the flight); the flight planning software does not guard against planning that aircraft through Class II airspace even though Class I was selected. The planning Dispatcher appears to have failed to double-check the route for compliance with FAR and equipment capabilities. The error was not identified until after flight departure; but before entering Class II airspace.
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.