 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 ng flight crew reported a track/heading deviation during departure from clt airport while on the BOBZY3 departure due to an apparent navigation database error.
| Attributes | |
| ACN | 1582560 |
| Time | |
| Date | 201810 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | CLT.TRACON |
| State Reference | NC |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | B737 Next Generation Undifferentiated |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Route In Use | SID BOBZY3 |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Navigation Database |
| Person 1 | |
| Function | Pilot Flying First Officer |
| Qualification | Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument |
| Experience | Flight Crew Total 6000 |
| Person 2 | |
| Function | Captain Pilot Not 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:
Aircraft made a turn direct nashville after crossing bobzy intersection on the BOBZY3 departure. Departure asked where we were direct to. We stated ZZZ. They came back and said we were the third aircraft in an hour to have done that and that it appeared the FMC was dropping the remaining fixes of the departure that would have taken us further west and then heading to ZZZ. The flight plan was checked on the ground in concurrence with SOP and all fixes appeared to be in order. ATC said they had cleared up our flight plan and not to worry about it; but that they would query companies on what might be occurring with the current navigation database upload.we also had a fleet manager on board who concurred with what ATC said. Apparently; this has been brought to the attention of the company recently due to the fact many of our aircraft have had this happen.company needs to have an alert sent out warning crews of this issue with the BOBZY3 at clt. Yet again; we have issues with automation out of this extremely over complex airport.
Original NASA ASRS Text
Title: B737 NG flight crew reported a track/heading deviation during departure from CLT airport while on the BOBZY3 departure due to an apparent navigation database error.
Narrative: Aircraft made a turn direct Nashville after crossing BOBZY Intersection on the BOBZY3 departure. Departure asked where we were direct to. We stated ZZZ. They came back and said we were the third aircraft in an hour to have done that and that it appeared the FMC was dropping the remaining fixes of the departure that would have taken us further west and THEN heading to ZZZ. The flight plan was checked on the ground in concurrence with SOP and all fixes appeared to be in order. ATC said they had cleared up our flight plan and not to worry about it; but that they would query companies on what might be occurring with the current navigation database upload.We also had a fleet manager on board who concurred with what ATC said. Apparently; this has been brought to the attention of the company recently due to the fact many of our aircraft have had this happen.Company needs to have an alert sent out warning crews of this issue with the BOBZY3 at CLT. Yet again; we have issues with automation out of this extremely over complex airport.
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.