 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Corporate aircraft flight crew reported temporary disorientation on departure due to initial heading not being in the database of the FMS.
| Attributes | |
| ACN | 1602550 |
| Time | |
| Date | 201812 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | DAL.Airport |
| State Reference | TX |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Medium Transport |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Climb |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument |
| Person 2 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Pax trip [from] dal. Dal ground changed our SID from KKITY4 departure to the WORTH1 departure off runway 31L. Sic changed the routing in the FMS. PIC then did the dual verification by reading the fixes from the FMS and sic verified from the departure plate that the read back was correct. What we did not catch is the FMS legs page routing does not reflect that the departure plate has a climb and right turn to a heading of 013. This is not reflected in the FMS when the procedure is loaded. Verifying all the fixes in the departure is insufficient to catch this. We did expect to takeoff on [runway] 31L and turn right. Sic pilot flying took off in roll mode with lnv armed. Upon reaching 400 AGL; the flight director prompted a left turn and we both were surprised and said to each other ' I thought we were supposed to turn right?'. Who is right? Us or the flight director with the programmed SID? It took a minute to decide we were right and we were correcting our heading when ATC issued a heading. Later; ATC asked us what we were navigating toward. He said we caught it in time but was curious because this happens on this departure a lot.I told him we had an automation guidance issue. I had not yet figured out the difference in the departure plate and the FMS legs page for this departure.we should have caught the discrepancy between the departure plate and the FMS but I believe this can happen again if people are not aware of this issue.I suggest operations issue a notice to make people aware of this trap and make jeppesen or whoever issues the database for the FMS aware.
Original NASA ASRS Text
Title: Corporate aircraft flight crew reported temporary disorientation on departure due to initial heading not being in the database of the FMS.
Narrative: Pax trip [from] DAL. DAL Ground changed our SID from KKITY4 departure to the WORTH1 departure off Runway 31L. SIC changed the routing in the FMS. PIC then did the dual verification by reading the fixes from the FMS and SIC verified from the Departure Plate that the read back was correct. What we did not catch is the FMS legs page routing does not reflect that the Departure Plate has a climb and RIGHT turn to a heading of 013. This is NOT reflected in the FMS when the procedure is loaded. Verifying all the fixes in the departure is insufficient to catch this. We did expect to takeoff on [Runway] 31L and turn right. SIC Pilot Flying took off in ROLL mode with LNV armed. Upon reaching 400 AGL; the flight director prompted a left turn and we both were surprised and said to each other ' I thought we were supposed to turn right?'. Who is right? Us or the Flight Director with the programmed SID? It took a minute to decide we were right and we were correcting our heading when ATC issued a heading. Later; ATC asked us what we were navigating toward. He said we caught it in time but was curious because this happens on this departure a lot.I told him we had an automation guidance issue. I had not yet figured out the difference in the Departure Plate and the FMS legs page for this departure.We should have caught the discrepancy between the Departure Plate and the FMS but I believe this can happen again if people are not aware of this issue.I suggest Operations issue a notice to make people aware of this trap and make Jeppesen or whoever issues the database for the FMS aware.
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.