Air carrier crew descends relying on a clearance given by approach controller who used their call sign in error when intending descent for another aircraft.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	451626
Time
Date	199910
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : phl.airport
State Reference	PA
Altitude	msl bound lower : 5000 msl bound upper : 6000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : phl.tracon
Operator	common carrier : air carrier
Make Model Name	B737-400
Operating Under FAR Part	Part 121
Navigation In Use	ils localizer & glide slope : 27l Other
Flight Phase	descent : intermediate altitude descent : approach
Route In Use	arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : private pilot : multi engine pilot : instrument pilot : commercial
Experience	flight time last 90 days : 250 flight time total : 17000 flight time type : 3500
ASRS Report	451626
Person 2
Affiliation	company : air carrier
Qualification	pilot : atp pilot : multi engine
Experience	flight time last 90 days : 150 flight time total : 3000 flight time type : 300
ASRS Report	451350
Events
Anomaly	altitude deviation : excursion from assigned altitude non adherence : published procedure non adherence : clearance
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	ATC Human Performance

Narrative:

While being vectored for the approach, control gave us a descent to 2100 ft MSL and a new heading. We read back the clearance with our call sign and proceeded as instructed. When passing through 5000 ft, approach control asked us what our intentions were. We repeated our clearance and he responded by saying that it was meant for a different aircraft. We then asked him what he would like us to do. He did not respond right away and then when he did he inquired about our intentions again. Finally we were instructed to maintain 3000 ft and fly a heading of 060 degrees. The remainder of the approach was uneventful. Upon gate arrival I phoned approach control and spoke with a supervisor who informed me that there was not a problem and that we were not in violation as we had proceeded as instructed. Furthermore, the controller had used the wrong call sign -- our call sign -- and never corrected the error, even after we read back the clearance with our call sign.

Original NASA ASRS Text

Title: ACR CREW DSNDS RELYING ON A CLRNC GIVEN BY APCH CTLR WHO USED THEIR CALL SIGN IN ERROR WHEN INTENDING DSCNT FOR ANOTHER ACFT.

Narrative: WHILE BEING VECTORED FOR THE APCH, CTL GAVE US A DSCNT TO 2100 FT MSL AND A NEW HDG. WE READ BACK THE CLRNC WITH OUR CALL SIGN AND PROCEEDED AS INSTRUCTED. WHEN PASSING THROUGH 5000 FT, APCH CTL ASKED US WHAT OUR INTENTIONS WERE. WE REPEATED OUR CLRNC AND HE RESPONDED BY SAYING THAT IT WAS MEANT FOR A DIFFERENT ACFT. WE THEN ASKED HIM WHAT HE WOULD LIKE US TO DO. HE DID NOT RESPOND RIGHT AWAY AND THEN WHEN HE DID HE INQUIRED ABOUT OUR INTENTIONS AGAIN. FINALLY WE WERE INSTRUCTED TO MAINTAIN 3000 FT AND FLY A HDG OF 060 DEGS. THE REMAINDER OF THE APCH WAS UNEVENTFUL. UPON GATE ARR I PHONED APCH CTL AND SPOKE WITH A SUPVR WHO INFORMED ME THAT THERE WAS NOT A PROB AND THAT WE WERE NOT IN VIOLATION AS WE HAD PROCEEDED AS INSTRUCTED. FURTHERMORE, THE CTLR HAD USED THE WRONG CALL SIGN -- OUR CALL SIGN -- AND NEVER CORRECTED THE ERROR, EVEN AFTER WE READ BACK THE CLRNC WITH OUR CALL SIGN.

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.