 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-400 aircraft in cruise received crossing restr altitude clearance. Captain put the altitude in the computer, but forgot what VNAV was inoperative and that the descent would have to be manual. Controller informed flight crew that they had missed the crossing restr.
| Attributes | |
| ACN | 358670 |
| Time | |
| Date | 199701 |
| Day | Sun |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : ric |
| State Reference | VA |
| Altitude | msl bound lower : 29000 msl bound upper : 33000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zdc |
| Operator | common carrier : air carrier |
| Make Model Name | B737-400 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other Other |
| Flight Phase | cruise other descent other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 40 flight time total : 9000 flight time type : 2000 |
| ASRS Report | 358670 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : instrument pilot : commercial pilot : atp |
| Experience | flight time last 90 days : 120 flight time total : 18700 flight time type : 10000 |
| ASRS Report | 358287 |
| Events | |
| Anomaly | altitude deviation : crossing restriction not met non adherence : clearance other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | none taken : detected after the fact other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
During cruise at FL330, ZDC issued a clearance to cross 65 mi south of richmond at FL290. The captain programmed the FMC with the crossing waypoint. When selecting the altitude, he put FL290 on the richmond waypoint and the 65 mi south waypoint. Vertical navigation (VNAV) function of the autoplt was inoperative, so the descent had to be selected manually. We both did not notice the 65 mi crossing restr drop off the FMC screen when we passed it, but I kept looking at the FL290 selected over richmond and believed that it was the FL290 crossing restr. At 50 mi south of richmond ATC informed us of the missed restr. Solution: enter the crossing restr only at the crossing point, pay closer attention and look at what the FMC says not what you expect to see.
Original NASA ASRS Text
Title: B737-400 ACFT IN CRUISE RECEIVED XING RESTR ALT CLRNC. CAPT PUT THE ALT IN THE COMPUTER, BUT FORGOT WHAT VNAV WAS INOP AND THAT THE DSCNT WOULD HAVE TO BE MANUAL. CTLR INFORMED FLC THAT THEY HAD MISSED THE XING RESTR.
Narrative: DURING CRUISE AT FL330, ZDC ISSUED A CLRNC TO CROSS 65 MI S OF RICHMOND AT FL290. THE CAPT PROGRAMMED THE FMC WITH THE XING WAYPOINT. WHEN SELECTING THE ALT, HE PUT FL290 ON THE RICHMOND WAYPOINT AND THE 65 MI S WAYPOINT. VERT NAV (VNAV) FUNCTION OF THE AUTOPLT WAS INOP, SO THE DSCNT HAD TO BE SELECTED MANUALLY. WE BOTH DID NOT NOTICE THE 65 MI XING RESTR DROP OFF THE FMC SCREEN WHEN WE PASSED IT, BUT I KEPT LOOKING AT THE FL290 SELECTED OVER RICHMOND AND BELIEVED THAT IT WAS THE FL290 XING RESTR. AT 50 MI S OF RICHMOND ATC INFORMED US OF THE MISSED RESTR. SOLUTION: ENTER THE XING RESTR ONLY AT THE XING POINT, PAY CLOSER ATTN AND LOOK AT WHAT THE FMC SAYS NOT WHAT YOU EXPECT TO SEE.
Data retrieved from NASA's ASRS site as of July 2007 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.