37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 551678 |
Time | |
Date | 200206 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : lax.airport |
State Reference | CA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Regional Jet CL65, Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 121 |
ASRS Report | 551678 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial pilot : cfi pilot : multi engine |
Experience | flight time last 90 days : 130 |
ASRS Report | 551456 |
Events | |
Anomaly | incursion : runway non adherence : published procedure |
Independent Detector | other controllera other flight crewa other flight crewb other other : 3 |
Resolutory Action | controller : separated traffic none taken : anomaly accepted other |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | ATC Human Performance Flight Crew Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Upon landing at lax runway 25L, we exited on high speed taxiway M to our right. We then proceeded across the runway 25R hold short line prior to being cleared across. As we rolled slowly toward the runway 25R edge, I began coming to a stop just as the tower controller cleared us across runway 25R, stating that an aircraft would be in position and hold on runway 25R awaiting takeoff. The tower controller made no communications with us after clearing us to land, up to the clearance to cross runway 25R. Even if not required, many controllers will issue a reminder to 'hold short' as we exit, especially if departing traffic are using the close parallel. Upon talking to the lax tower supervisor, he informed me that he doesn't issue such reminders because they require a readback from the pilot and if the pilot fails to give the readback, then the controller is partly liable. He informed me that our aircraft was observed past the hold line and that no incursion or loss of separation occurred. Contributing factors are the closely-spaced runways, the lack of a taxiway between the runways (like I'm used to in phx), and the lack of communication from the controller, and the inconsistent use of hold short reminders by tower controllers. Supplemental information from acn 551456: tower supervisor said he did not specifically issue a hold short instruction because 1) it's not required, and 2) if we fail to read it back to him then he is partly liable if we don't comply with the instruction. Therefore, some controllers do issue hold short instructions (like in phoenix, as we are used to) and others don't.
Original NASA ASRS Text
Title: AFTER LNDG LAX RWY 25L, A CL65 CREW PROCEEDED TO CROSS RWY 25R WITHOUT A SPECIFIC CLRNC TO DO SO.
Narrative: UPON LNDG AT LAX RWY 25L, WE EXITED ON HIGH SPD TXWY M TO OUR R. WE THEN PROCEEDED ACROSS THE RWY 25R HOLD SHORT LINE PRIOR TO BEING CLRED ACROSS. AS WE ROLLED SLOWLY TOWARD THE RWY 25R EDGE, I BEGAN COMING TO A STOP JUST AS THE TWR CTLR CLRED US ACROSS RWY 25R, STATING THAT AN ACFT WOULD BE IN POS AND HOLD ON RWY 25R AWAITING TKOF. THE TWR CTLR MADE NO COMS WITH US AFTER CLRING US TO LAND, UP TO THE CLRNC TO CROSS RWY 25R. EVEN IF NOT REQUIRED, MANY CTLRS WILL ISSUE A REMINDER TO 'HOLD SHORT' AS WE EXIT, ESPECIALLY IF DEPARTING TFC ARE USING THE CLOSE PARALLEL. UPON TALKING TO THE LAX TWR SUPVR, HE INFORMED ME THAT HE DOESN'T ISSUE SUCH REMINDERS BECAUSE THEY REQUIRE A READBACK FROM THE PLT AND IF THE PLT FAILS TO GIVE THE READBACK, THEN THE CTLR IS PARTLY LIABLE. HE INFORMED ME THAT OUR ACFT WAS OBSERVED PAST THE HOLD LINE AND THAT NO INCURSION OR LOSS OF SEPARATION OCCURRED. CONTRIBUTING FACTORS ARE THE CLOSELY-SPACED RWYS, THE LACK OF A TXWY BTWN THE RWYS (LIKE I'M USED TO IN PHX), AND THE LACK OF COM FROM THE CTLR, AND THE INCONSISTENT USE OF HOLD SHORT REMINDERS BY TWR CTLRS. SUPPLEMENTAL INFO FROM ACN 551456: TWR SUPVR SAID HE DID NOT SPECIFICALLY ISSUE A HOLD SHORT INSTRUCTION BECAUSE 1) IT'S NOT REQUIRED, AND 2) IF WE FAIL TO READ IT BACK TO HIM THEN HE IS PARTLY LIABLE IF WE DON'T COMPLY WITH THE INSTRUCTION. THEREFORE, SOME CTLRS DO ISSUE HOLD SHORT INSTRUCTIONS (LIKE IN PHOENIX, AS WE ARE USED TO) AND OTHERS DON'T.
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.