37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 345970 |
Time | |
Date | 199608 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : gck |
State Reference | KS |
Altitude | msl bound lower : 28000 msl bound upper : 29000 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zdv |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | descent other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | observation : company check pilot |
Qualification | pilot : atp |
Experience | flight time last 90 days : 100 flight time total : 7000 flight time type : 700 |
ASRS Report | 345970 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | altitude deviation : overshoot non adherence : clearance |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
I was instructor pilot for first time captain during initial IOE. Flight was on descent, cleared from cruise altitude to FL290. The PF was the IOE captain. He entered FL290 in the flight control panel and I confirmed the entry as descent was initiated. I took out our performance computer to enter our landing information. As I was making the entries, ZDV called and instructed us to maintain 280 KTS. The PF didn't catch the transmission fully and I said to him '280' (two eighty) as he pointed at the flight control panel. I returned to the performance computer and after about 2 mins looked at our altimeter and realized (with horror) that we were level at FL280! Agghh! I immediately reported the mix-up to den, and after a long long pause, the controller said, 'that's ok, continue descent.' cause: 1) my failure as instructor pilot to effectively monitor the 'new guy.' 2) the 'new guy's' failure to use company altitude verification procedures. He thought I meant for him to enter FL280. He then entered that altitude and did not ask for verification of the new altitude from the PNF (me) -- a violation of SOP. Had he asked for verification, the error would have been caught immediately.
Original NASA ASRS Text
Title: FLC OF A WDB OVERSHOT DSCNT ALT DUE TO THE PF MISUNDERSTANDING OF AN AIRSPD RESTR FOR ALT.
Narrative: I WAS INSTRUCTOR PLT FOR FIRST TIME CAPT DURING INITIAL IOE. FLT WAS ON DSCNT, CLRED FROM CRUISE ALT TO FL290. THE PF WAS THE IOE CAPT. HE ENTERED FL290 IN THE FLT CTL PANEL AND I CONFIRMED THE ENTRY AS DSCNT WAS INITIATED. I TOOK OUT OUR PERFORMANCE COMPUTER TO ENTER OUR LNDG INFO. AS I WAS MAKING THE ENTRIES, ZDV CALLED AND INSTRUCTED US TO MAINTAIN 280 KTS. THE PF DIDN'T CATCH THE XMISSION FULLY AND I SAID TO HIM '280' (TWO EIGHTY) AS HE POINTED AT THE FLT CTL PANEL. I RETURNED TO THE PERFORMANCE COMPUTER AND AFTER ABOUT 2 MINS LOOKED AT OUR ALTIMETER AND REALIZED (WITH HORROR) THAT WE WERE LEVEL AT FL280! AGGHH! I IMMEDIATELY RPTED THE MIX-UP TO DEN, AND AFTER A LONG LONG PAUSE, THE CTLR SAID, 'THAT'S OK, CONTINUE DSCNT.' CAUSE: 1) MY FAILURE AS INSTRUCTOR PLT TO EFFECTIVELY MONITOR THE 'NEW GUY.' 2) THE 'NEW GUY'S' FAILURE TO USE COMPANY ALT VERIFICATION PROCS. HE THOUGHT I MEANT FOR HIM TO ENTER FL280. HE THEN ENTERED THAT ALT AND DID NOT ASK FOR VERIFICATION OF THE NEW ALT FROM THE PNF (ME) -- A VIOLATION OF SOP. HAD HE ASKED FOR VERIFICATION, THE ERROR WOULD HAVE BEEN CAUGHT IMMEDIATELY.
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.