37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 730041 |
Time | |
Date | 200703 |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : lgb.airport |
State Reference | CA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : cwa.tower |
Operator | common carrier : air carrier |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
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 : 250 flight time total : 10000 flight time type : 3000 |
ASRS Report | 730041 |
Person 2 | |
Affiliation | government : faa |
Function | controller : local |
Events | |
Anomaly | conflict : ground less severe incursion : runway non adherence : far non adherence : published procedure |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Airport Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Situations | |
Chart | airport : lgb.airport |
Narrative:
Landed on runway 30 at lgb after being cleared to land by lgb tower. I had planned on exiting the runway 30 at taxiway K to go to the air carrier ramp. The PF (first officer) landed a little long and we could not make taxiway K which is a reverse turn kind of exit. We exited on runway 34L/K area but in the runway area of runway 25R. With no place to go we contacted ground control while stopped at runways 34L/25R/30/K area. Lgb instructed or informed us that we were on an active runway and an aircraft was going around because of that. I think the aircraft was on approach to runway 25R but I am not sure-- maybe runway 34L? This lgb airport is very confusing and with multiple runways in use with numerous aircraft types the potential for unsafe sits is very high with regard to runway incursions. Suggestions: 1) better brief of planned runway exit after landing. 2) more communication with tower -- planned exit; not just a 'contact ground when clear.' 3) be aware of landing traffic on intersecting runways without lahso clearance. 4) hotspots are not marked as such as lgb commercial chart. 5) better runway exit points for large aircraft operations.
Original NASA ASRS Text
Title: AN ACR ACFT LANDING ON LGB RWY 30 EXITED ON RWY 7L/25R AND HELD ON THE ACTIVE RWY CAUSING AN ACFT TO GAR.
Narrative: LANDED ON RWY 30 AT LGB AFTER BEING CLRED TO LAND BY LGB TWR. I HAD PLANNED ON EXITING THE RWY 30 AT TXWY K TO GO TO THE ACR RAMP. THE PF (FO) LANDED A LITTLE LONG AND WE COULD NOT MAKE TXWY K WHICH IS A REVERSE TURN KIND OF EXIT. WE EXITED ON RWY 34L/K AREA BUT IN THE RWY AREA OF RWY 25R. WITH NO PLACE TO GO WE CONTACTED GND CTL WHILE STOPPED AT RWYS 34L/25R/30/K AREA. LGB INSTRUCTED OR INFORMED US THAT WE WERE ON AN ACTIVE RWY AND AN ACFT WAS GOING AROUND BECAUSE OF THAT. I THINK THE ACFT WAS ON APCH TO RWY 25R BUT I AM NOT SURE-- MAYBE RWY 34L? THIS LGB ARPT IS VERY CONFUSING AND WITH MULTIPLE RWYS IN USE WITH NUMEROUS ACFT TYPES THE POTENTIAL FOR UNSAFE SITS IS VERY HIGH WITH REGARD TO RWY INCURSIONS. SUGGESTIONS: 1) BETTER BRIEF OF PLANNED RWY EXIT AFTER LNDG. 2) MORE COM WITH TWR -- PLANNED EXIT; NOT JUST A 'CONTACT GND WHEN CLR.' 3) BE AWARE OF LNDG TFC ON INTERSECTING RWYS WITHOUT LAHSO CLRNC. 4) HOTSPOTS ARE NOT MARKED AS SUCH AS LGB COMMERCIAL CHART. 5) BETTER RWY EXIT POINTS FOR LARGE ACFT OPS.
Data retrieved from NASA's ASRS site as of January 2009 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.