37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 306239 |
Time | |
Date | 199506 |
Day | Sun |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : ogd |
State Reference | UT |
Altitude | msl bound lower : 17000 msl bound upper : 24000 |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zlc |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | 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 : 250 flight time total : 5000 flight time type : 1900 |
ASRS Report | 306239 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 270 flight time total : 7500 flight time type : 270 |
ASRS Report | 306570 |
Events | |
Anomaly | altitude deviation : crossing restriction not met non adherence : clearance |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : returned to intended course or assigned course other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Flight XXXX cleared to cross bearr at 17000 ft. I missed the altitude by 7000 ft, because of my failure to compute my descent point properly. Neither center or approach gave me any indication that there was any conflict. The flight continued with no other occurrences. Callback conversation with reporter revealed the following: reporter stated that simply the error happened because a good conversation was taking place. The flight crew had been issued a descent clearance with a 'pilot discretion' to meet the crossing restr. Reporter states that another contributing factor was that there was too little activity -- even for the controller. The controller felt bad because he didn't catch the mistake, either. Upon discovery, the flight crew frantically began a descent, but they were literally over the intersection and had to confess. Note: air carrier policy does not support the use of FMS for descent profiles. Flight continued uneventfully. Supplemental information from acn 306570: we were late to start our descent and crossed bearr at 22000 ft.
Original NASA ASRS Text
Title: NON-COMPLIANCE BY B737-300 FLC TO MEET XING RESTR. 'PLT DISCRETION' CLRNC WAS NEVER INITIATED.
Narrative: FLT XXXX CLRED TO CROSS BEARR AT 17000 FT. I MISSED THE ALT BY 7000 FT, BECAUSE OF MY FAILURE TO COMPUTE MY DSCNT POINT PROPERLY. NEITHER CTR OR APCH GAVE ME ANY INDICATION THAT THERE WAS ANY CONFLICT. THE FLT CONTINUED WITH NO OTHER OCCURRENCES. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: RPTR STATED THAT SIMPLY THE ERROR HAPPENED BECAUSE A GOOD CONVERSATION WAS TAKING PLACE. THE FLC HAD BEEN ISSUED A DSCNT CLRNC WITH A 'PLT DISCRETION' TO MEET THE XING RESTR. RPTR STATES THAT ANOTHER CONTRIBUTING FACTOR WAS THAT THERE WAS TOO LITTLE ACTIVITY -- EVEN FOR THE CTLR. THE CTLR FELT BAD BECAUSE HE DIDN'T CATCH THE MISTAKE, EITHER. UPON DISCOVERY, THE FLC FRANTICALLY BEGAN A DSCNT, BUT THEY WERE LITERALLY OVER THE INTXN AND HAD TO CONFESS. NOTE: ACR POLICY DOES NOT SUPPORT THE USE OF FMS FOR DSCNT PROFILES. FLT CONTINUED UNEVENTFULLY. SUPPLEMENTAL INFO FROM ACN 306570: WE WERE LATE TO START OUR DSCNT AND CROSSED BEARR AT 22000 FT.
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.