37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 373650 |
Time | |
Date | 199707 |
Day | Tue |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | atc facility : omn airport : mco |
State Reference | FL |
Altitude | msl bound lower : 11000 msl bound upper : 12000 |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B757 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | descent other |
Route In Use | arrival other arrival star : star enroute airway : mco |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : commercial pilot : instrument pilot : flight engineer |
Experience | flight time last 90 days : 200 flight time total : 15000 flight time type : 1200 |
ASRS Report | 373650 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : flight engineer pilot : cfi pilot : atp |
Experience | flight time last 90 days : 80 flight time total : 5000 flight time type : 750 |
ASRS Report | 373641 |
Events | |
Anomaly | altitude deviation : overshoot altitude deviation : crossing restriction not met non adherence : clearance other anomaly other |
Independent Detector | other controllera |
Resolutory Action | flight crew : returned to intended course or assigned course other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | other |
Narrative:
Descending into mco, north of omn on bitho 7 arrival, had preprogrammed FMC to expect lamma 250 KTS, 12000 ft. First officer flying. I was busy monitoring route and radar due to thunderstorm in area, talking to passenger, and advising flight attendants. Cleared to cross lamma at 250 KTS and (I set 11000 ft in MCP)? First officer pointed to and acknowledged altimeter set per SOP. Level at 11000 ft and approaching lamma, center told us to climb to 12000 ft. I acknowledged but said we were at 11000 ft already and did he actually mean climb to 12000 ft. Controller said our cleared altitude had been 12000 ft, not 11000 ft. We acknowledged but told controller we understood we had been cleared previously to 11000 ft. Subsequently climbed to 12000 ft and were changed to orl approach. Without listening to ATC tapes, I honestly don't know whether controller erred (misspoke) or whether we were at fault. All our SOP's are designed to preclude such an occurrence (to prevent our failure) and we follow them religiously. Bottom line: a mistake was made either by ATC or by us, and the procedures used by all should have, but did not, prevent the error. I do not think changes to SOP or procedures are warranted. The good news is the system is working! The error was caught and corrected in a timely manner -- regardless of the error source!
Original NASA ASRS Text
Title: B757 ACFT ON STAR ARR HEARD, RESPONDED, AND SET 11000 FT AS ASSIGNED ALT. ARTCC RADAR CTLR TOLD THEM THAT THE ASSIGNED WAS 12000 FT SO FLC CLBED TO 12000 FT.
Narrative: DSNDING INTO MCO, N OF OMN ON BITHO 7 ARR, HAD PREPROGRAMMED FMC TO EXPECT LAMMA 250 KTS, 12000 FT. FO FLYING. I WAS BUSY MONITORING RTE AND RADAR DUE TO TSTM IN AREA, TALKING TO PAX, AND ADVISING FLT ATTENDANTS. CLRED TO CROSS LAMMA AT 250 KTS AND (I SET 11000 FT IN MCP)? FO POINTED TO AND ACKNOWLEDGED ALTIMETER SET PER SOP. LEVEL AT 11000 FT AND APCHING LAMMA, CTR TOLD US TO CLB TO 12000 FT. I ACKNOWLEDGED BUT SAID WE WERE AT 11000 FT ALREADY AND DID HE ACTUALLY MEAN CLB TO 12000 FT. CTLR SAID OUR CLRED ALT HAD BEEN 12000 FT, NOT 11000 FT. WE ACKNOWLEDGED BUT TOLD CTLR WE UNDERSTOOD WE HAD BEEN CLRED PREVIOUSLY TO 11000 FT. SUBSEQUENTLY CLBED TO 12000 FT AND WERE CHANGED TO ORL APCH. WITHOUT LISTENING TO ATC TAPES, I HONESTLY DON'T KNOW WHETHER CTLR ERRED (MISSPOKE) OR WHETHER WE WERE AT FAULT. ALL OUR SOP'S ARE DESIGNED TO PRECLUDE SUCH AN OCCURRENCE (TO PREVENT OUR FAILURE) AND WE FOLLOW THEM RELIGIOUSLY. BOTTOM LINE: A MISTAKE WAS MADE EITHER BY ATC OR BY US, AND THE PROCS USED BY ALL SHOULD HAVE, BUT DID NOT, PREVENT THE ERROR. I DO NOT THINK CHANGES TO SOP OR PROCS ARE WARRANTED. THE GOOD NEWS IS THE SYS IS WORKING! THE ERROR WAS CAUGHT AND CORRECTED IN A TIMELY MANNER -- REGARDLESS OF THE ERROR SOURCE!
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.