37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 353798 |
Time | |
Date | 199611 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
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 |
Operator | common carrier : air carrier |
Make Model Name | B737-500 |
Operating Under FAR Part | Part 121 |
Navigation In Use | ils localizer & glide slope : ioss Other Other |
Flight Phase | cruise other descent : approach |
Route In Use | approach : visual |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : flight engineer pilot : commercial pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 4000 flight time type : 100 |
ASRS Report | 353798 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : commercial pilot : flight engineer pilot : instrument |
Experience | flight time last 90 days : 194 flight time total : 6021 flight time type : 1577 |
ASRS Report | 354044 |
Events | |
Anomaly | non adherence : clearance non adherence : published procedure other anomaly other other spatial deviation |
Independent Detector | other controllera other flight crewa |
Resolutory Action | flight crew : became reoriented flight crew : returned to intended course or assigned course other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Situations | |
Airport | other physical facility |
Narrative:
ATC provided a vector for base to runway 24R at lax for a visual approach to follow a B737 turning final. The field, including both runway complexes, was in sight from downwind and during the initial turn to base. I was 'padlocked' to the B737 traffic as the haze became a factor while looking into the sun. The ILS to runway 24R was OTS and we indicated from our FMS we were slightly south of extended centerline. We were both concerned with 'sequencing' ourselves reference our traffic and were not monitoring our instruments accurately. As we rolled out on final, I mentioned a ground reference I had not previously noticed. We both simultaneously realized our problem as lax tower called to send us to the proper set of runways. The requirement for pilots to pick up visual contact on competing arriving traffic while maneuvering to final is a necessity at all busy stations to keep traffic flowing. It is critical for pilots to use all means available and divide duties to ensure there is no traffic conflict first and then to navigation as accurately as possible. We attempted to do both, but fixated on the first. While there was no safety issue due to our clearing, we were in a position not anticipated by ATC and could have been a conflict to unknown traffic. FMC's should be monitore D at the smallest scales appropriate and other available navaids used. (We briefed ILS runway 24L as backup to runway 24R, but didn't use it, as we confidently called visual only to lose it.) further, there should be procedure and no 'retribution' for being an airfield in the sun momentarily. Our maneuver is done routinely at lax with little problem. We simply overshot due to prioritizing traffic over runway lineup and then believing the runways in front of us were the right ones.
Original NASA ASRS Text
Title: AN ACR B737-500 LINED UP ON THE S RWYS AT LAX. IT WAS CLRED TO THE N SIDE.
Narrative: ATC PROVIDED A VECTOR FOR BASE TO RWY 24R AT LAX FOR A VISUAL APCH TO FOLLOW A B737 TURNING FINAL. THE FIELD, INCLUDING BOTH RWY COMPLEXES, WAS IN SIGHT FROM DOWNWIND AND DURING THE INITIAL TURN TO BASE. I WAS 'PADLOCKED' TO THE B737 TFC AS THE HAZE BECAME A FACTOR WHILE LOOKING INTO THE SUN. THE ILS TO RWY 24R WAS OTS AND WE INDICATED FROM OUR FMS WE WERE SLIGHTLY S OF EXTENDED CTRLINE. WE WERE BOTH CONCERNED WITH 'SEQUENCING' OURSELVES REF OUR TFC AND WERE NOT MONITORING OUR INSTS ACCURATELY. AS WE ROLLED OUT ON FINAL, I MENTIONED A GND REF I HAD NOT PREVIOUSLY NOTICED. WE BOTH SIMULTANEOUSLY REALIZED OUR PROB AS LAX TWR CALLED TO SEND US TO THE PROPER SET OF RWYS. THE REQUIREMENT FOR PLTS TO PICK UP VISUAL CONTACT ON COMPETING ARRIVING TFC WHILE MANEUVERING TO FINAL IS A NECESSITY AT ALL BUSY STATIONS TO KEEP TFC FLOWING. IT IS CRITICAL FOR PLTS TO USE ALL MEANS AVAILABLE AND DIVIDE DUTIES TO ENSURE THERE IS NO TFC CONFLICT FIRST AND THEN TO NAV AS ACCURATELY AS POSSIBLE. WE ATTEMPTED TO DO BOTH, BUT FIXATED ON THE FIRST. WHILE THERE WAS NO SAFETY ISSUE DUE TO OUR CLRING, WE WERE IN A POS NOT ANTICIPATED BY ATC AND COULD HAVE BEEN A CONFLICT TO UNKNOWN TFC. FMC'S SHOULD BE MONITORE D AT THE SMALLEST SCALES APPROPRIATE AND OTHER AVAILABLE NAVAIDS USED. (WE BRIEFED ILS RWY 24L AS BACKUP TO RWY 24R, BUT DIDN'T USE IT, AS WE CONFIDENTLY CALLED VISUAL ONLY TO LOSE IT.) FURTHER, THERE SHOULD BE PROC AND NO 'RETRIBUTION' FOR BEING AN AIRFIELD IN THE SUN MOMENTARILY. OUR MANEUVER IS DONE ROUTINELY AT LAX WITH LITTLE PROB. WE SIMPLY OVERSHOT DUE TO PRIORITIZING TFC OVER RWY LINEUP AND THEN BELIEVING THE RWYS IN FRONT OF US WERE THE RIGHT ONES.
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.