37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 538277 |
Time | |
Date | 200202 |
Day | Tue |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : new.airport |
State Reference | LA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air taxi |
Make Model Name | Citation V |
Operating Under FAR Part | Part 135 |
Navigation In Use | other |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air taxi |
Function | flight crew : captain oversight : pic |
Qualification | pilot : multi engine pilot : atp pilot : cfi |
Experience | flight time last 90 days : 70 flight time total : 3800 flight time type : 145 |
ASRS Report | 538277 |
Person 2 | |
Affiliation | company : air taxi |
Function | flight crew : first officer |
Qualification | pilot : atp |
Events | |
Anomaly | incursion : runway non adherence : clearance non adherence : far non adherence : published procedure |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Our starting position was on the FBO ramp when we were instructed to taxi to runway 36L. The sic (who was also ATP, type-rated, and captain qualified on the aircraft) was the PF and taxiing, while I was the PNF performing the checklist duties. The FBO ramp is near the approach end of runway 36L, and actually adjoins the taxiway which leads to runway 36L (no grass in between the two) so the taxi distance is very short. As we started to taxi, I began to perform the taxi checklist. As we progressed, I looked outside to monitor the taxi and noticed runway hold line markings off to our right side, so I immediately told the sic to stop. After assessing the situation, I determined that we were sitting on a paved area that was marked with diagonal yellow lines, just prior to the taxiway edge line/markings that defined the taxiway leading to runway 36L. We were also just west of the runway hold line which is on the taxiway leading to runway 36L. I came to the conclusion that, while we were sitting on an area marked with the diagonal lines, we were still in an area that was part of the FBO ramp space as we had not yet crossed the taxiway edge line. I was concerned, however, that we were west of the runway hold line that was on the taxiway. Neither ground control nor the tower said anything. No aircraft landed on runway 36L during this time either. I believe the factors contributing to this event were: the PF's inattn to the taxi/ramp pavement markings combined with the PNF not fully monitoring the taxi due to the distraction of running checklists. Contributing to this was the very short taxi distance, and the somewhat confusing markings at that intersection. I feel the area where the FBO ramp joins the taxiway should be marked with a runway hold short line along the entire length -- not just on the taxiway itself.
Original NASA ASRS Text
Title: A C560 CREW, TAXIING FOR TKOF AT KNEW, TAXIED PAST A HOLD SHORT LINE.
Narrative: OUR STARTING POS WAS ON THE FBO RAMP WHEN WE WERE INSTRUCTED TO TAXI TO RWY 36L. THE SIC (WHO WAS ALSO ATP, TYPE-RATED, AND CAPT QUALIFIED ON THE ACFT) WAS THE PF AND TAXIING, WHILE I WAS THE PNF PERFORMING THE CHKLIST DUTIES. THE FBO RAMP IS NEAR THE APCH END OF RWY 36L, AND ACTUALLY ADJOINS THE TXWY WHICH LEADS TO RWY 36L (NO GRASS IN BTWN THE TWO) SO THE TAXI DISTANCE IS VERY SHORT. AS WE STARTED TO TAXI, I BEGAN TO PERFORM THE TAXI CHKLIST. AS WE PROGRESSED, I LOOKED OUTSIDE TO MONITOR THE TAXI AND NOTICED RWY HOLD LINE MARKINGS OFF TO OUR R SIDE, SO I IMMEDIATELY TOLD THE SIC TO STOP. AFTER ASSESSING THE SIT, I DETERMINED THAT WE WERE SITTING ON A PAVED AREA THAT WAS MARKED WITH DIAGONAL YELLOW LINES, JUST PRIOR TO THE TXWY EDGE LINE/MARKINGS THAT DEFINED THE TXWY LEADING TO RWY 36L. WE WERE ALSO JUST W OF THE RWY HOLD LINE WHICH IS ON THE TXWY LEADING TO RWY 36L. I CAME TO THE CONCLUSION THAT, WHILE WE WERE SITTING ON AN AREA MARKED WITH THE DIAGONAL LINES, WE WERE STILL IN AN AREA THAT WAS PART OF THE FBO RAMP SPACE AS WE HAD NOT YET CROSSED THE TXWY EDGE LINE. I WAS CONCERNED, HOWEVER, THAT WE WERE W OF THE RWY HOLD LINE THAT WAS ON THE TXWY. NEITHER GND CTL NOR THE TWR SAID ANYTHING. NO ACFT LANDED ON RWY 36L DURING THIS TIME EITHER. I BELIEVE THE FACTORS CONTRIBUTING TO THIS EVENT WERE: THE PF'S INATTN TO THE TAXI/RAMP PAVEMENT MARKINGS COMBINED WITH THE PNF NOT FULLY MONITORING THE TAXI DUE TO THE DISTR OF RUNNING CHKLISTS. CONTRIBUTING TO THIS WAS THE VERY SHORT TAXI DISTANCE, AND THE SOMEWHAT CONFUSING MARKINGS AT THAT INTXN. I FEEL THE AREA WHERE THE FBO RAMP JOINS THE TXWY SHOULD BE MARKED WITH A RWY HOLD SHORT LINE ALONG THE ENTIRE LENGTH -- NOT JUST ON THE TXWY ITSELF.
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.