 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Unfamiliar with publication airport; flight crew of B737-300 cross faded hold line of runway 26L while taxiing to runway 26R.
| Attributes | |
| ACN | 738015 |
| Time | |
| Date | 200705 |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : pub.airport |
| State Reference | CO |
| Altitude | agl single value : 0 |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : taxi |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Experience | flight time last 90 days : 150 flight time total : 4500 flight time type : 150 |
| ASRS Report | 738015 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Experience | flight time last 90 days : 200 flight time total : 11300 flight time type : 8400 |
| ASRS Report | 738014 |
| Events | |
| Anomaly | incursion : runway |
| Independent Detector | other flight crewa other flight crewb |
| Resolutory Action | none taken : detected after the fact |
| Supplementary | |
| Problem Areas | ATC Human Performance Airport Chart Or Publication Flight Crew Human Performance |
| Primary Problem | Airport |
Narrative:
Diverted to publication for thunderstorms in den. Refueled and redispatched in pueblo; and on taxi out ground control told us to taxi to runway 26R. We started taxi and we had to call dispatch via cell phone to get perf information on runway 26R. They had been reporting use of runway 17 on ATIS; so we had not gotten the perf for runway 26 when we spoke earlier with dispatch. No communication via ACARS in publication so I called dispatch on my cell phone while the captain was taxiing. We had been parked on the main ramp which intersects runway 26L. No gate in publication. When we turned out toward runway 26R we went over the poorly marked hold lines for runway 26L. The ramp and the runway are the same paved surface with only faded hold lines marking the runway. No mention was made by ATC; and no other aircraft were affected by our incursion. Nothing is denoted on the commercial chart page as a hot spot.callback conversation with reporter revealed the following information: the captain advised that the event occurred in daylight hours and the ramp was clear and dry. The only difficulty in seeing the runway was the faded markings.
Original NASA ASRS Text
Title: UNFAMILIAR WITH PUB ARPT; FLT CREW OF B737-300 CROSS FADED HOLD LINE OF RWY 26L WHILE TAXIING TO RWY 26R.
Narrative: DIVERTED TO PUB FOR THUNDERSTORMS IN DEN. REFUELED AND REDISPATCHED IN PUEBLO; AND ON TAXI OUT GND CTL TOLD US TO TAXI TO RWY 26R. WE STARTED TAXI AND WE HAD TO CALL DISPATCH VIA CELL PHONE TO GET PERF INFO ON RWY 26R. THEY HAD BEEN REPORTING USE OF RWY 17 ON ATIS; SO WE HAD NOT GOTTEN THE PERF FOR RWY 26 WHEN WE SPOKE EARLIER WITH DISPATCH. NO COM VIA ACARS IN PUB SO I CALLED DISPATCH ON MY CELL PHONE WHILE THE CAPT WAS TAXIING. WE HAD BEEN PARKED ON THE MAIN RAMP WHICH INTERSECTS RWY 26L. NO GATE IN PUB. WHEN WE TURNED OUT TOWARD RWY 26R WE WENT OVER THE POORLY MARKED HOLD LINES FOR RWY 26L. THE RAMP AND THE RWY ARE THE SAME PAVED SURFACE WITH ONLY FADED HOLD LINES MARKING THE RWY. NO MENTION WAS MADE BY ATC; AND NO OTHER ACFT WERE AFFECTED BY OUR INCURSION. NOTHING IS DENOTED ON THE COMMERCIAL CHART PAGE AS A HOT SPOT.CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE CAPT ADVISED THAT THE EVENT OCCURRED IN DAYLIGHT HRS AND THE RAMP WAS CLR AND DRY. THE ONLY DIFFICULTY IN SEEING THE RWY WAS THE FADED MARKINGS.
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.