 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Confusion reigned between ATC and the flight crew of a B737NG with respect to both track and altitude as the flight approached its destination. An FMC stored company route which ended at a fix prior to the destination airport was cited as a contributing factor.
| Attributes | |
| ACN | 1154457 |
| Time | |
| Date | 201403 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | FNT.Airport |
| State Reference | MI |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Navigation Database |
| Person 1 | |
| Function | Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 202 Flight Crew Type 7500 |
| Person 2 | |
| Function | First Officer |
| Experience | Flight Crew Last 90 Days 316 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Clearance |
Narrative:
ATC cleared us to cross qubee at 11;000. We selected 11;000 in the window and FMC and let VNAV descend on profile. Around 18;000 we switched to approach who gave us 7;000; which we put in the window and deleted the 11;000 in FMC. We then descended in level change as a bit high for visual profile. Approaching qubee; it was the last point in the FMC under XXXFNT01 profile; the captain had the first officer ask for heading out of qubee. Approach responded direct fnt which agreed with the flight plan. We added that point; verbalized; verified; and monitored LNAV to fnt. Rest of flight was uneventful.as far as we were concerned; all altitudes were complied with and as we asked two to three miles before qubee. We flew correct route to fnt. Tower wanted us to call regarding qubee. We called flight operations; who talked with ATC; who agreed no altitude violation occurred. [They need to [m]ake sure approach states 'comply with previous restriction' if they want 11;000 [at qubee].
Original NASA ASRS Text
Title: Confusion reigned between ATC and the flight crew of a B737NG with respect to both track and altitude as the flight approached its destination. An FMC stored company route which ended at a fix prior to the destination airport was cited as a contributing factor.
Narrative: ATC cleared us to cross QUBEE at 11;000. We selected 11;000 in the window and FMC and let VNAV descend on profile. Around 18;000 we switched to Approach who gave us 7;000; which we put in the window and deleted the 11;000 in FMC. We then descended in Level Change as a bit high for visual profile. Approaching QUBEE; it was the last point in the FMC under XXXFNT01 profile; the Captain had the First Officer ask for heading out of QUBEE. Approach responded direct FNT which agreed with the flight plan. We added that point; verbalized; verified; and monitored LNAV to FNT. Rest of flight was uneventful.As far as we were concerned; all altitudes were complied with and as we asked two to three miles before QUBEE. We flew correct route to FNT. Tower wanted us to call regarding QUBEE. We called Flight Operations; who talked with ATC; who agreed no altitude violation occurred. [They need to [m]ake sure Approach states 'comply with previous restriction' if they want 11;000 [at QUBEE].
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.