37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 255755 |
Time | |
Date | 199311 |
Day | Wed |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : zmp airport : msp |
State Reference | MS |
Altitude | msl bound lower : 13000 msl bound upper : 13000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
Flight Phase | descent other |
Route In Use | arrival other enroute airway : zmp |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | Medium Transport, High Wing, 2 Turboprop Eng |
Flight Phase | descent other |
Route In Use | arrival other |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller non radar : 14 controller radar : 12 controller supervisory : 3 |
ASRS Report | 255755 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 15500 |
ASRS Report | 255995 |
Events | |
Anomaly | altitude deviation : excursion from assigned altitude conflict : airborne less severe non adherence : required legal separation non adherence : clearance non adherence : published procedure |
Independent Detector | atc equipment other atc equipment : unspecified other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : investigated |
Miss Distance | horizontal : 21000 vertical : 0 |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error Pilot Deviation |
Narrative:
Air carrier X was descending to FL240 on the meinz arrival to msp. Aircraft was issued 17000 ft with an expect peppr at 10000 ft. Pilot read back descend to 17000 ft, cross peppr at 10000 ft. I did not catch erroneous readback. Later, air carrier X was issued 16000 ft. Pilot read back and asked if we still wanted peppr at 10000 ft. We replied affirmative, thinking pilot just dropped word 'expect.' when air carrier X descended below 16000 ft conflict alert activated with an aircraft level at 6000 ft. I then tried to figure out why conflict alert had activated. After I realized this aircraft was not a factor, I then saw that air carrier X was overtaking a turboprop, air carrier Y. I then tried to issue altitudes to maintain separation but was unable. As separation was lost, conflict alert activated. Supplemental information from acn 255995: on meinz 6 arrival into msp, I was given a speed reduction to 260 KTS, and a descent from 25000 ft to 17000 ft with a restr to cross peppr intersection at 10000 ft. The first officer read back the clearance to 'maintain 17000 ft, cross peppr at 10000 ft.' while descending through 18500 ft, the controller told us to maintain 16000 ft. The first officer responded 'maintain 16000 ft, do you still want us at 10000 ft at peppr?' controller responded 'affirmative.' first officer, 'roger, we're continuing our descent.' at 13200 ft the controller told us to maintain 14000 ft. I informed the controller, through the first officer, 'we're at 13200 ft, do you want us to climb back to 14000 ft?' controller's response: 'descend to 10000 ft, expedite your descent.' controller then instructed another aircraft to climb to 14000 ft immediately. Upon landing msp, I called inspector and spoke with a supervisor to get clarification on what had occurred. I was advised by the supervisor that our initial clearance was to descend to 17000 ft and expect to cross peppr at 10000 ft. He then informed me they were pulling the ATC tapes to find out exactly what transpired. After reviewing the tapes, supervisor indicated the controller issued the instruction to 'expect to cross peppr at 10000 ft.' however, the first officer read back the descent clearance to cross peppr at 10000 ft and was not corrected by the controller. Because of this breakdown in communication, my aircraft came within 4.6 mi of a 2ND aircraft. The supervisor also indicated that this was a controller error and would be handled internally. I feel that the use of the term 'expect' can cause confusion and lead to misinterp if not correctly assimilated by both pilot and controller.
Original NASA ASRS Text
Title: CTLR TELLS ACR TO 'EXPECT' TO CROSS INTXN AT 10000 FT. PLT DOESN'T HEAR 'EXPECT' AND STARTS DSCNT RESULTING IN LTSS.
Narrative: ACR X WAS DSNDING TO FL240 ON THE MEINZ ARR TO MSP. ACFT WAS ISSUED 17000 FT WITH AN EXPECT PEPPR AT 10000 FT. PLT READ BACK DSND TO 17000 FT, CROSS PEPPR AT 10000 FT. I DID NOT CATCH ERRONEOUS READBACK. LATER, ACR X WAS ISSUED 16000 FT. PLT READ BACK AND ASKED IF WE STILL WANTED PEPPR AT 10000 FT. WE REPLIED AFFIRMATIVE, THINKING PLT JUST DROPPED WORD 'EXPECT.' WHEN ACR X DSNDED BELOW 16000 FT CONFLICT ALERT ACTIVATED WITH AN ACFT LEVEL AT 6000 FT. I THEN TRIED TO FIGURE OUT WHY CONFLICT ALERT HAD ACTIVATED. AFTER I REALIZED THIS ACFT WAS NOT A FACTOR, I THEN SAW THAT ACR X WAS OVERTAKING A TURBOPROP, ACR Y. I THEN TRIED TO ISSUE ALTS TO MAINTAIN SEPARATION BUT WAS UNABLE. AS SEPARATION WAS LOST, CONFLICT ALERT ACTIVATED. SUPPLEMENTAL INFORMATION FROM ACN 255995: ON MEINZ 6 ARR INTO MSP, I WAS GIVEN A SPD REDUCTION TO 260 KTS, AND A DSCNT FROM 25000 FT TO 17000 FT WITH A RESTR TO CROSS PEPPR INTXN AT 10000 FT. THE FO READ BACK THE CLRNC TO 'MAINTAIN 17000 FT, CROSS PEPPR AT 10000 FT.' WHILE DSNDING THROUGH 18500 FT, THE CTLR TOLD US TO MAINTAIN 16000 FT. THE FO RESPONDED 'MAINTAIN 16000 FT, DO YOU STILL WANT US AT 10000 FT AT PEPPR?' CTLR RESPONDED 'AFFIRMATIVE.' FO, 'ROGER, WE'RE CONTINUING OUR DSCNT.' AT 13200 FT THE CTLR TOLD US TO MAINTAIN 14000 FT. I INFORMED THE CTLR, THROUGH THE FO, 'WE'RE AT 13200 FT, DO YOU WANT US TO CLB BACK TO 14000 FT?' CTLR'S RESPONSE: 'DSND TO 10000 FT, EXPEDITE YOUR DSCNT.' CTLR THEN INSTRUCTED ANOTHER ACFT TO CLB TO 14000 FT IMMEDIATELY. UPON LNDG MSP, I CALLED INSPECTOR AND SPOKE WITH A SUPVR TO GET CLARIFICATION ON WHAT HAD OCCURRED. I WAS ADVISED BY THE SUPVR THAT OUR INITIAL CLRNC WAS TO DSND TO 17000 FT AND EXPECT TO CROSS PEPPR AT 10000 FT. HE THEN INFORMED ME THEY WERE PULLING THE ATC TAPES TO FIND OUT EXACTLY WHAT TRANSPIRED. AFTER REVIEWING THE TAPES, SUPVR INDICATED THE CTLR ISSUED THE INSTRUCTION TO 'EXPECT TO CROSS PEPPR AT 10000 FT.' HOWEVER, THE FO READ BACK THE DSCNT CLRNC TO CROSS PEPPR AT 10000 FT AND WAS NOT CORRECTED BY THE CTLR. BECAUSE OF THIS BREAKDOWN IN COM, MY ACFT CAME WITHIN 4.6 MI OF A 2ND ACFT. THE SUPVR ALSO INDICATED THAT THIS WAS A CTLR ERROR AND WOULD BE HANDLED INTERNALLY. I FEEL THAT THE USE OF THE TERM 'EXPECT' CAN CAUSE CONFUSION AND LEAD TO MISINTERP IF NOT CORRECTLY ASSIMILATED BY BOTH PLT AND CTLR.
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.