After being cleared for a visual approach to las runway 25 left, on contact with the local controller, crew believed they were cleared on and read back runway 25 right.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	586207
Time
Date	200306
Day	Sun
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : las.airport
State Reference	NV
Altitude	msl bound lower : 2181 msl bound upper : 5000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tower : las.tower
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach landing : roll
Route In Use	approach : visual
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
ASRS Report	586207
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
ASRS Report	586516
Events
Anomaly	incursion : runway non adherence : clearance non adherence : published procedure
Independent Detector	other controllera other flight crewa other flight crewb
Resolutory Action	none taken : detected after the fact
Consequence	faa : investigated faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error Pilot Deviation

Narrative:

We were cleared for a visual approach to runway 25L. When we switched to tower, we thought that we heard, 'cleared to land runway 25R.' the captain responded with 'roger, cleared to land on the right,' to which there was no correction or response. After landing on runway 25R, we were told to call tower, which pulled the tapes, and verified that they had actually said cleared to land on runway 25L. The controller did not catch the incorrect read back of 'cleared to land on the right.' supplemental information from acn 586516: I acknowledged 'cleared to land on the right side' and landed on the runway 25R without incident or traffic separation problems. I heard the clearance wrong, and the controller failed to catch my erroneous readback. I did hear the tape, and it did say 'cleared to land runway 25I.' I don't know how I heard it wrong. I did not query again, because I was certain of what I heard, and made what seemed a glaring reply, which went unchallenged.

Original NASA ASRS Text

Title: AFTER BEING CLRED FOR A VISUAL APCH TO LAS RWY 25 L, ON CONTACT WITH THE LCL CTLR, CREW BELIEVED THEY WERE CLRED ON AND READ BACK RWY 25 R.

Narrative: WE WERE CLRED FOR A VISUAL APCH TO RWY 25L. WHEN WE SWITCHED TO TWR, WE THOUGHT THAT WE HEARD, 'CLRED TO LAND RWY 25R.' THE CAPT RESPONDED WITH 'ROGER, CLRED TO LAND ON THE R,' TO WHICH THERE WAS NO CORRECTION OR RESPONSE. AFTER LANDING ON RWY 25R, WE WERE TOLD TO CALL TWR, WHICH PULLED THE TAPES, AND VERIFIED THAT THEY HAD ACTUALLY SAID CLRED TO LAND ON RWY 25L. THE CTLR DID NOT CATCH THE INCORRECT READ BACK OF 'CLRED TO LAND ON THE R.' SUPPLEMENTAL INFO FROM ACN 586516: I ACKNOWLEDGED 'CLRED TO LAND ON THE R SIDE' AND LANDED ON THE RWY 25R WITHOUT INCIDENT OR TFC SEPARATION PROBS. I HEARD THE CLRNC WRONG, AND THE CTLR FAILED TO CATCH MY ERRONEOUS READBACK. I DID HEAR THE TAPE, AND IT DID SAY 'CLRED TO LAND RWY 25I.' I DON'T KNOW HOW I HEARD IT WRONG. I DID NOT QUERY AGAIN, BECAUSE I WAS CERTAIN OF WHAT I HEARD, AND MADE WHAT SEEMED A GLARING REPLY, WHICH WENT UNCHALLENGED.

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.