 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Mix up in descent clearance caused air carrier to descent through altitude expected by receiving center controller. Operational deviation.
| Attributes | |
| ACN | 94447 |
| Time | |
| Date | 198809 |
| Day | Sun |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | atc facility : dqn |
| State Reference | OH |
| Altitude | msl bound lower : 24000 msl bound upper : 35000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | artcc : zid artcc : zob tower : ord |
| Operator | common carrier : air carrier |
| Make Model Name | Large Transport, Low Wing, 3 Turbojet Eng |
| Flight Phase | descent other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 60 flight time total : 15000 flight time type : 3000 |
| ASRS Report | 94447 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : instrument pilot : commercial pilot : flight engineer |
| Experience | flight time last 90 days : 160 flight time total : 5600 flight time type : 3000 |
| ASRS Report | 94541 |
| Events | |
| Anomaly | altitude deviation : overshoot |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Deviation Inter Facility Coordination Failure other |
Narrative:
On ZID frequency 128.7, cruising at FL350, given clearance to cross 10 NM south dqn at FL240. Read back entire clearance. After descent begun we were handed off to next controller on 132.7 (may have been ZOB). Upon check in called descending to FL240. Controller said descend to FL310. Verified clearance with controller and stopped at FL310 (we were at about FL317 when handed off). Controller asked if ZID had given us 10 south dqn at FL240. Replied affirmative. Asked if we read back entire clearance or just rogered. Replied we had read entire clearance. We asked if that was the clearance we should have had. Center replied, no, should have been cross 10 south dqn at FL330. First officer flying aircraft, captain talking radio. Keep running clearance log and read back as written down. Another failure to communication and verify. When will we get data link and eliminate this kind of error? Data link could not only eliminate this source of error, but would decongest control frequencys greatly.
Original NASA ASRS Text
Title: MIX UP IN DESCENT CLRNC CAUSED ACR TO DESCENT THROUGH ALT EXPECTED BY RECEIVING CENTER CTLR. OPERATIONAL DEVIATION.
Narrative: ON ZID FREQ 128.7, CRUISING AT FL350, GIVEN CLRNC TO CROSS 10 NM S DQN AT FL240. READ BACK ENTIRE CLRNC. AFTER DSCNT BEGUN WE WERE HANDED OFF TO NEXT CTLR ON 132.7 (MAY HAVE BEEN ZOB). UPON CHECK IN CALLED DSNDING TO FL240. CTLR SAID DSND TO FL310. VERIFIED CLRNC WITH CTLR AND STOPPED AT FL310 (WE WERE AT ABOUT FL317 WHEN HANDED OFF). CTLR ASKED IF ZID HAD GIVEN US 10 S DQN AT FL240. REPLIED AFFIRMATIVE. ASKED IF WE READ BACK ENTIRE CLRNC OR JUST ROGERED. REPLIED WE HAD READ ENTIRE CLRNC. WE ASKED IF THAT WAS THE CLRNC WE SHOULD HAVE HAD. CENTER REPLIED, NO, SHOULD HAVE BEEN CROSS 10 S DQN AT FL330. F/O FLYING ACFT, CAPT TALKING RADIO. KEEP RUNNING CLRNC LOG AND READ BACK AS WRITTEN DOWN. ANOTHER FAILURE TO COM AND VERIFY. WHEN WILL WE GET DATA LINK AND ELIMINATE THIS KIND OF ERROR? DATA LINK COULD NOT ONLY ELIMINATE THIS SOURCE OF ERROR, BUT WOULD DECONGEST CTL FREQS GREATLY.
Data retrieved from NASA's ASRS site as of August 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.