37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 436550 |
Time | |
Date | 199905 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | intersection : arnes |
State Reference | CA |
Altitude | msl single value : 10000 |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : sct.tracon |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Navigation In Use | ils localizer only : 25l other |
Flight Phase | descent : approach descent : intermediate altitude |
Route In Use | approach : instrument precision arrival star : paradise 3 |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 18000 flight time type : 12500 |
ASRS Report | 436550 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : cfi pilot : atp pilot : flight engineer |
Experience | flight time last 90 days : 240 flight time total : 4700 |
ASRS Report | 436266 |
Events | |
Anomaly | non adherence : published procedure non adherence : clearance other spatial deviation |
Independent Detector | atc equipment other atc equipment : radar other controllera other flight crewa |
Resolutory Action | controller : issued advisory controller : issued new clearance flight crew : returned to intended course |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We were flight tus-lax. Our LNAV was programmed for the pdz 3 arrival to intercept the runway 25L localizer at arnes. This is usually the proper arrival into lax from the tucson area. As captain, I was flying the airplane, and the first officer was handling the radios. Somewhere prior to arnes we were given a new clearance which was to intercept the runway 24R localizer at mitts. I never heard this transmission and the first officer acknowledged the clearance, but did not update the LNAV for the new clearance. At arnes the aircraft intercepted the runway 25L localizer. The first officer asked me where I was going and I indicated I was intercepting runway 25 as per our clearance. He informed me that the clearance had changed and he thought I knew that. We began turning back to the arrival when the controller inquired what we were doing. We told him that we had made a mistake and were trying to correct it. Vectors were given to runway 24R localizer and the rest of the flight went as planned. Our communication on the flight deck broke down which caused this mistake. I don't know why I didn't hear the new clearance and I don't know why the LNAV was not updated. Supplemental information from acn 436266: we were cleared the arrival and intercept the runway 24R localizer. The LNAV was not changed for the appropriate runway and began to turn to intercept runway 25L. After about 70 degrees of turn we realized it was turning too soon, we began to turn back towards the pdz arrival while at the same time approach says, 'it looks like you're intercepting runway 25L' and then gave us a vector towards runway 24R.
Original NASA ASRS Text
Title: A B737-300 PIC FAILS TO FOLLOW THE ARR PROC AS AMENDED BY LAX APCH CTL INTO LAX, CA.
Narrative: WE WERE FLT TUS-LAX. OUR LNAV WAS PROGRAMMED FOR THE PDZ 3 ARR TO INTERCEPT THE RWY 25L LOC AT ARNES. THIS IS USUALLY THE PROPER ARR INTO LAX FROM THE TUCSON AREA. AS CAPT, I WAS FLYING THE AIRPLANE, AND THE FO WAS HANDLING THE RADIOS. SOMEWHERE PRIOR TO ARNES WE WERE GIVEN A NEW CLRNC WHICH WAS TO INTERCEPT THE RWY 24R LOC AT MITTS. I NEVER HEARD THIS XMISSION AND THE FO ACKNOWLEDGED THE CLRNC, BUT DID NOT UPDATE THE LNAV FOR THE NEW CLRNC. AT ARNES THE ACFT INTERCEPTED THE RWY 25L LOC. THE FO ASKED ME WHERE I WAS GOING AND I INDICATED I WAS INTERCEPTING RWY 25 AS PER OUR CLRNC. HE INFORMED ME THAT THE CLRNC HAD CHANGED AND HE THOUGHT I KNEW THAT. WE BEGAN TURNING BACK TO THE ARR WHEN THE CTLR INQUIRED WHAT WE WERE DOING. WE TOLD HIM THAT WE HAD MADE A MISTAKE AND WERE TRYING TO CORRECT IT. VECTORS WERE GIVEN TO RWY 24R LOC AND THE REST OF THE FLT WENT AS PLANNED. OUR COM ON THE FLT DECK BROKE DOWN WHICH CAUSED THIS MISTAKE. I DON'T KNOW WHY I DIDN'T HEAR THE NEW CLRNC AND I DON'T KNOW WHY THE LNAV WAS NOT UPDATED. SUPPLEMENTAL INFO FROM ACN 436266: WE WERE CLRED THE ARR AND INTERCEPT THE RWY 24R LOC. THE LNAV WAS NOT CHANGED FOR THE APPROPRIATE RWY AND BEGAN TO TURN TO INTERCEPT RWY 25L. AFTER ABOUT 70 DEGS OF TURN WE REALIZED IT WAS TURNING TOO SOON, WE BEGAN TO TURN BACK TOWARDS THE PDZ ARR WHILE AT THE SAME TIME APCH SAYS, 'IT LOOKS LIKE YOU'RE INTERCEPTING RWY 25L' AND THEN GAVE US A VECTOR TOWARDS RWY 24R.
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.