 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-700 flight crew reports programing the FMC for ten north of the fix instead of ten south as required; resulting in a missed crossing restriction. Fatigue was cited as a factor in the incident.
| Attributes | |
| ACN | 969049 |
| Time | |
| Date | 201109 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZFW.ARTCC |
| State Reference | TX |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | First Officer |
| Experience | Flight Crew Last 90 Days 231 |
| Person 2 | |
| Function | Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 204 |
| Events | |
| Anomaly | Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Clearance |
Narrative:
Programmed the crossing restriction as ten north of fwa; when it should have been ten south; at FL240 (fwa/10 versus fwa/-10). Failed to identify the programming error until ATC pointed out that we looked high; issuing a traffic alert. I have been on an a.M. Line this month and last. The day began with a late show time and was not scheduled to end until well after dark. Due to the late aircraft arrival; another lengthy delay for late connecting bags; a complicated mechanical issue; an associated maintenance delay and unscheduled swap; the already busy six-leg day became much more involved. Due to the short nature of all the legs and rapid tempo; climbing straight into descent; we both were quite worn out by the end of the day. Lobby time was in the morning. The prior day; lobby time was four hours earlier. We have a.M. And P.M. Trips for a reason; so pilots aren't bouncing between sleep cycles during the pairing. Unfortunately; that is exactly what we were scheduled to do. Keep pairings within the typical a.M. And P.M. Footprint. If the day is stretched; don't schedule a six-leg day.
Original NASA ASRS Text
Title: B737-700 flight crew reports programing the FMC for ten north of the fix instead of ten south as required; resulting in a missed crossing restriction. Fatigue was cited as a factor in the incident.
Narrative: Programmed the crossing restriction as ten north of FWA; when it should have been ten south; at FL240 (FWA/10 versus FWA/-10). Failed to identify the programming error until ATC pointed out that we looked high; issuing a Traffic Alert. I have been on an A.M. line this month and last. The day began with a late show time and was not scheduled to end until well after dark. Due to the late aircraft arrival; another lengthy delay for late connecting bags; a complicated mechanical issue; an associated maintenance delay and unscheduled swap; the already busy six-leg day became much more involved. Due to the short nature of all the legs and rapid tempo; climbing straight into descent; we both were quite worn out by the end of the day. Lobby time was in the morning. The prior day; lobby time was four hours earlier. We have A.M. and P.M. trips for a reason; so pilots aren't bouncing between sleep cycles during the pairing. Unfortunately; that is exactly what we were scheduled to do. Keep pairings within the typical A.M. and P.M. footprint. If the day is stretched; don't schedule a six-leg day.
Data retrieved from NASA's ASRS site as of April 2012 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.