37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 396130 |
Time | |
Date | 199802 |
Day | Thu |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : lax |
State Reference | CA |
Altitude | msl bound lower : 2500 msl bound upper : 2500 |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Controlling Facilities | tower : lax tower : sdf |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | descent : approach |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : flight engineer pilot : commercial pilot : cfi pilot : atp |
Experience | flight time last 90 days : 191 flight time total : 10750 flight time type : 4500 |
ASRS Report | 396130 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
Events | |
Anomaly | non adherence : clearance non adherence : far other spatial deviation |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : returned to intended course or assigned course |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
3RD leg of a high volume, shuttle operation, tired crew. We were initially cleared for a visual approach to runway 24R, lax then subsequently cleared for a visual approach to runway 24L. I thought I heard runway 25L. As we proceeded on our base the alert first officer pointed out the error and I hard turned the aircraft to line up with runway 24L. I was anticipating a runway change to runway 25L and so 'wishfully heard' the clearance. We only slightly overshot the runway 24L final and had the south complex traffic in sight at all times so safety was never compromised. However, but for an alert first officer, it could have been. Some lax controllers also state the ILS frequency when reassigning runways. This is an excellent practice and could prevent misunderstandings.
Original NASA ASRS Text
Title: AN ACR B737 FLC OVERSHOT THEIR TURN TO THE FINAL APCH COURSE DURING A VISUAL APCH TO A PARALLEL RWY WHEN THE CAPT BECAME CONFUSED AS TO WHICH RWY HE WAS CLRED TO APCH. THE FO CORRECTED HIM IN TIME TO MINIMIZE THE OVERSHOOT.
Narrative: 3RD LEG OF A HIGH VOLUME, SHUTTLE OP, TIRED CREW. WE WERE INITIALLY CLRED FOR A VISUAL APCH TO RWY 24R, LAX THEN SUBSEQUENTLY CLRED FOR A VISUAL APCH TO RWY 24L. I THOUGHT I HEARD RWY 25L. AS WE PROCEEDED ON OUR BASE THE ALERT FO POINTED OUT THE ERROR AND I HARD TURNED THE ACFT TO LINE UP WITH RWY 24L. I WAS ANTICIPATING A RWY CHANGE TO RWY 25L AND SO 'WISHFULLY HEARD' THE CLRNC. WE ONLY SLIGHTLY OVERSHOT THE RWY 24L FINAL AND HAD THE S COMPLEX TFC IN SIGHT AT ALL TIMES SO SAFETY WAS NEVER COMPROMISED. HOWEVER, BUT FOR AN ALERT FO, IT COULD HAVE BEEN. SOME LAX CTLRS ALSO STATE THE ILS FREQ WHEN REASSIGNING RWYS. THIS IS AN EXCELLENT PRACTICE AND COULD PREVENT MISUNDERSTANDINGS.
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.