37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 611430 |
Time | |
Date | 200403 |
Day | Mon |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : sps.airport |
State Reference | TX |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air taxi |
Make Model Name | King Air C90 E90 |
Operating Under FAR Part | Part 135 |
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 |
Experience | flight time last 90 days : 75 flight time total : 3300 flight time type : 800 |
ASRS Report | 611430 |
Person 2 | |
Affiliation | company : air taxi |
Function | flight crew : first officer |
Qualification | pilot : cfi pilot : instrument pilot : multi engine pilot : commercial |
Experience | flight time last 90 days : 125 flight time total : 1425 flight time type : 550 |
ASRS Report | 611428 |
Events | |
Anomaly | incursion : runway non adherence : clearance non adherence : published procedure non adherence : far other anomaly other |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Airport ATC Human Performance Chart Or Publication Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We were on the GA ramp at sheppard air force base, wichita falls municipal, on mar/mon/04. Incident occurred at XA20 in the morning. While on the ramp we received taxi clearance 'taxi to runway 17,' with no specific instructions. Leaving the ramp, we turned left on taxiway C, crossed runway 17, and proceeded up taxiway a. After traveling 300-400 yards on taxiway a, the controller asked where we were. We responded we were on taxiway a. He then advised us that we had illegally crossed runway 17. We stopped and reexamined the airport diagram, at which point we saw an alternative route which would have precluded crossing runway 17. In our haste, we had gone with the first route we had seen. At this time, I explained our failure to see another route and apologized. There were no traffic conflicts during this incident. Why? Hurried too much. Should have looked for alternative rtes. Should have asked controller for directions. Should have asked for clarification about crossing the runway. Lack of knowledge -- misunderstood regulation. Corrective actions: slow down. Ask for progressive taxi. Re-familiarize myself with far/aim. I was mistaken in my belief that I could cross a runway I had been cleared to. It won't happen again! Supplemental information from acn 611428: we were cleared across the runway because we were not given any hold short of the runway instructions and could cross all runways to get to our destination runway. Apologized to the controller and told him about our miscom/misconception due to the ambiguous taxi instructions. There was no other traffic using the runway at the time of the incident.
Original NASA ASRS Text
Title: UNAUTH RWY ENTRY, RWY INCURSION WHEN A BE9L FLT CREW CROSSES THE DEP END OF THE ACTIVE RWY AT SPS, TX.
Narrative: WE WERE ON THE GA RAMP AT SHEPPARD AIR FORCE BASE, WICHITA FALLS MUNI, ON MAR/MON/04. INCIDENT OCCURRED AT XA20 IN THE MORNING. WHILE ON THE RAMP WE RECEIVED TAXI CLRNC 'TAXI TO RWY 17,' WITH NO SPECIFIC INSTRUCTIONS. LEAVING THE RAMP, WE TURNED L ON TXWY C, CROSSED RWY 17, AND PROCEEDED UP TXWY A. AFTER TRAVELING 300-400 YARDS ON TXWY A, THE CTLR ASKED WHERE WE WERE. WE RESPONDED WE WERE ON TXWY A. HE THEN ADVISED US THAT WE HAD ILLEGALLY CROSSED RWY 17. WE STOPPED AND REEXAMINED THE ARPT DIAGRAM, AT WHICH POINT WE SAW AN ALTERNATIVE RTE WHICH WOULD HAVE PRECLUDED XING RWY 17. IN OUR HASTE, WE HAD GONE WITH THE FIRST RTE WE HAD SEEN. AT THIS TIME, I EXPLAINED OUR FAILURE TO SEE ANOTHER RTE AND APOLOGIZED. THERE WERE NO TFC CONFLICTS DURING THIS INCIDENT. WHY? HURRIED TOO MUCH. SHOULD HAVE LOOKED FOR ALTERNATIVE RTES. SHOULD HAVE ASKED CTLR FOR DIRECTIONS. SHOULD HAVE ASKED FOR CLARIFICATION ABOUT XING THE RWY. LACK OF KNOWLEDGE -- MISUNDERSTOOD REG. CORRECTIVE ACTIONS: SLOW DOWN. ASK FOR PROGRESSIVE TAXI. RE-FAMILIARIZE MYSELF WITH FAR/AIM. I WAS MISTAKEN IN MY BELIEF THAT I COULD CROSS A RWY I HAD BEEN CLRED TO. IT WON'T HAPPEN AGAIN! SUPPLEMENTAL INFO FROM ACN 611428: WE WERE CLRED ACROSS THE RWY BECAUSE WE WERE NOT GIVEN ANY HOLD SHORT OF THE RWY INSTRUCTIONS AND COULD CROSS ALL RWYS TO GET TO OUR DEST RWY. APOLOGIZED TO THE CTLR AND TOLD HIM ABOUT OUR MISCOM/MISCONCEPTION DUE TO THE AMBIGUOUS TAXI INSTRUCTIONS. THERE WAS NO OTHER TFC USING THE RWY AT THE TIME OF THE INCIDENT.
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.