37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 164389 |
Time | |
Date | 199011 |
Day | Tue |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : cle |
State Reference | OH |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
Flight Phase | ground : holding ground other : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : flight engineer pilot : cfi pilot : atp |
Experience | flight time last 90 days : 120 flight time total : 7800 flight time type : 2800 |
ASRS Report | 164389 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Events | |
Anomaly | incursion : runway non adherence : clearance other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | Other |
Supplementary | |
Primary Problem | Airport |
Air Traffic Incident | Pilot Deviation |
Situations | |
Airport | other physical facility |
Narrative:
As captain of air carrier flight xx, I crossed runway hold line west/O ATC clearance. I am concerned about the safety implications of this airport situation and am not filing this report for the immunity benefits (although that's nice, too). Attached is an airport diagram. Our flight taxied from the gate (which is northeast of the control tower) to runway 23L. As we taxied we skirted the east and north portions of the tarmac and then proceeded onto runway 28 in order to hold short of runway 23L. Remember the FARS and aim state that when cleared to taxi to a particular runway, the pilot may cross any intersecting runways that are along his taxi path, but may not cross the assigned runway unless specifically advised otherwise by ATC. Therefore, I proceeded slightly onto runway 27. That's when I realized that runway holding lines for runway 23L were also those for runway 28. There is a rather wide throat of txwys intersecting where this took place; i.e., the ramp area, intersecting with taxiway lima. In any event, the markings are unclr. I called alpa air safety about this, and as it turned out, in 9/90 another pilot from my airline reported that runway 23R is also included with this holding line. Better signs, markings are necessary. Otherwise a pilot will think that it is ok to cross runway 28, and usually it is, but once he does this, he discovers that he has encroached into the departure runways holding area. Callback conversation with reporter revealed the following: callback conducted with airport operations at cle hopkins airport. That person interviewed allowed as to how this problem does exist and has resulted in several runway transgressions. He states that the problem is currently being worked with FAA certification branch as well as several air carrier reps. However, no solution has been reached as of this date. It is clear that this is an ongoing and potentially dangerous problem.
Original NASA ASRS Text
Title: ACR MLG INADVERTENTLY CROSSED RWY HOLD LINE WHILE TAXIING FOR TKOF.
Narrative: AS CAPT OF ACR FLT XX, I CROSSED RWY HOLD LINE W/O ATC CLRNC. I AM CONCERNED ABOUT THE SAFETY IMPLICATIONS OF THIS ARPT SITUATION AND AM NOT FILING THIS RPT FOR THE IMMUNITY BENEFITS (ALTHOUGH THAT'S NICE, TOO). ATTACHED IS AN ARPT DIAGRAM. OUR FLT TAXIED FROM THE GATE (WHICH IS NE OF THE CTL TWR) TO RWY 23L. AS WE TAXIED WE SKIRTED THE E AND N PORTIONS OF THE TARMAC AND THEN PROCEEDED ONTO RWY 28 IN ORDER TO HOLD SHORT OF RWY 23L. REMEMBER THE FARS AND AIM STATE THAT WHEN CLRED TO TAXI TO A PARTICULAR RWY, THE PLT MAY CROSS ANY INTERSECTING RWYS THAT ARE ALONG HIS TAXI PATH, BUT MAY NOT CROSS THE ASSIGNED RWY UNLESS SPECIFICALLY ADVISED OTHERWISE BY ATC. THEREFORE, I PROCEEDED SLIGHTLY ONTO RWY 27. THAT'S WHEN I REALIZED THAT RWY HOLDING LINES FOR RWY 23L WERE ALSO THOSE FOR RWY 28. THERE IS A RATHER WIDE THROAT OF TXWYS INTERSECTING WHERE THIS TOOK PLACE; I.E., THE RAMP AREA, INTERSECTING WITH TXWY LIMA. IN ANY EVENT, THE MARKINGS ARE UNCLR. I CALLED ALPA AIR SAFETY ABOUT THIS, AND AS IT TURNED OUT, IN 9/90 ANOTHER PLT FROM MY AIRLINE RPTED THAT RWY 23R IS ALSO INCLUDED WITH THIS HOLDING LINE. BETTER SIGNS, MARKINGS ARE NECESSARY. OTHERWISE A PLT WILL THINK THAT IT IS OK TO CROSS RWY 28, AND USUALLY IT IS, BUT ONCE HE DOES THIS, HE DISCOVERS THAT HE HAS ENCROACHED INTO THE DEP RWYS HOLDING AREA. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: CALLBACK CONDUCTED WITH ARPT OPS AT CLE HOPKINS ARPT. THAT PERSON INTERVIEWED ALLOWED AS TO HOW THIS PROB DOES EXIST AND HAS RESULTED IN SEVERAL RWY TRANSGRESSIONS. HE STATES THAT THE PROB IS CURRENTLY BEING WORKED WITH FAA CERTIFICATION BRANCH AS WELL AS SEVERAL ACR REPS. HOWEVER, NO SOLUTION HAS BEEN REACHED AS OF THIS DATE. IT IS CLR THAT THIS IS AN ONGOING AND POTENTIALLY DANGEROUS PROB.
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.