37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1053156 |
Time | |
Date | 201212 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | EMB ERJ 170/175 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Cruising at FL350 fat; dumb; and tired we were told to cross [a fix] at FL310. The first officer was the pilot flying. He entered FL310 in the altitude window. We both pointed and confirmed. He entered the crossing restriction in the FMS; I confirmed and he activated. We both went back to staring out the window. I heard ATC tell someone to descend to FL310 and the first officer and I simultaneously realized we were less than a mile from the fix still at FL350. He initiated the descent; I called ATC. The controller made a couple other calls; and then told us to descend and maintain FL310 as well as a frequency change. I acknowledged and said thank you; he said no problem. The flight continued uneventfully. The fact is we flat out screwed up. We both thought we confirmed we were in VNAV. We watched the airplane closely on the remaining VNAV applications; it worked fine so I can only think we did not engage VNAV upon receiving the crossing restriction. We were both fatigued and had actually discussed taking coordinated naps about an hour prior to this happening; but neither of us did.... The first officer was sick the entire trip and not sleeping well. We had very early morning shows two days in a row. The simple fact is we didn't operate the airplane properly.
Original NASA ASRS Text
Title: ERJ170 flight crew missed a crossing restriction after failing to activate VNAV until alerted by ATC. Captain listed fatigue as a contributing factor.
Narrative: Cruising at FL350 fat; dumb; and tired we were told to cross [a fix] at FL310. The First Officer was the pilot flying. He entered FL310 in the altitude window. We both pointed and confirmed. He entered the crossing restriction in the FMS; I confirmed and he activated. We both went back to staring out the window. I heard ATC tell someone to descend to FL310 and the First Officer and I simultaneously realized we were less than a mile from the fix still at FL350. He initiated the descent; I called ATC. The Controller made a couple other calls; and then told us to descend and maintain FL310 as well as a frequency change. I acknowledged and said thank you; he said no problem. The flight continued uneventfully. The fact is we flat out screwed up. We both thought we confirmed we were in VNAV. We watched the airplane closely on the remaining VNAV applications; it worked fine so I can only think we did not engage VNAV upon receiving the crossing restriction. We were both fatigued and had actually discussed taking coordinated naps about an hour prior to this happening; but neither of us did.... The First Officer was sick the entire trip and not sleeping well. We had very early morning shows two days in a row. The simple fact is we didn't operate the airplane properly.
Data retrieved from NASA's ASRS site as of July 2013 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.