37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 449870 |
Time | |
Date | 199909 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : i69.airport |
State Reference | OH |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | Bonanza 35 |
Operating Under FAR Part | Part 91 |
Flight Phase | ground : taxi |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Navigation In Use | other |
Flight Phase | landing : go around |
Route In Use | approach : traffic pattern |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : private |
Experience | flight time last 90 days : 15 flight time total : 850 flight time type : 350 |
ASRS Report | 449870 |
Person 2 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : student |
Events | |
Anomaly | conflict : airborne less severe conflict : ground less severe incursion : runway non adherence : published procedure |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | flight crew : executed go around flight crew : took evasive action |
Miss Distance | horizontal : 1500 vertical : 300 |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Uncontrolled airport. Aircraft #1 crossed active runway while aircraft #2 was on short final for the runway. Aircraft #2 executed a go around. Horizontal miss distance estimated at 1000-1500 ft. In 40 yrs of flying, I have never caused another aircraft to go around. Very embarrassing! Why did it happen? I radioed my intent to cross and looked left first, saw nothing, then looked right. Started to roll across active runway. Then looked left again, saw aircraft #2 high and slightly outside the runway threshold. Applied full power to cross 65 ft runway. I looked, but did not see -- why I do not know. Most likely it occurred because my taxi direction to the only crossing intersection was with my back to the landing traffic on a runway that is parallel to the taxiway. Thus requiring a 90 degree turn to cross, which is where I looked. From now on, I will recognize that intersection for the hazard it is and take additional precaution in crossing.
Original NASA ASRS Text
Title: BEECH CRAFT PLT CROSSES RWY AT UNCTLED ARPT CAUSING GAR BY ACFT ON SHORT FINAL.
Narrative: UNCTLED ARPT. ACFT #1 CROSSED ACTIVE RWY WHILE ACFT #2 WAS ON SHORT FINAL FOR THE RWY. ACFT #2 EXECUTED A GAR. HORIZ MISS DISTANCE ESTIMATED AT 1000-1500 FT. IN 40 YRS OF FLYING, I HAVE NEVER CAUSED ANOTHER ACFT TO GO AROUND. VERY EMBARRASSING! WHY DID IT HAPPEN? I RADIOED MY INTENT TO CROSS AND LOOKED L FIRST, SAW NOTHING, THEN LOOKED R. STARTED TO ROLL ACROSS ACTIVE RWY. THEN LOOKED L AGAIN, SAW ACFT #2 HIGH AND SLIGHTLY OUTSIDE THE RWY THRESHOLD. APPLIED FULL PWR TO CROSS 65 FT RWY. I LOOKED, BUT DID NOT SEE -- WHY I DO NOT KNOW. MOST LIKELY IT OCCURRED BECAUSE MY TAXI DIRECTION TO THE ONLY XING INTXN WAS WITH MY BACK TO THE LNDG TFC ON A RWY THAT IS PARALLEL TO THE TXWY. THUS REQUIRING A 90 DEG TURN TO CROSS, WHICH IS WHERE I LOOKED. FROM NOW ON, I WILL RECOGNIZE THAT INTXN FOR THE HAZARD IT IS AND TAKE ADDITIONAL PRECAUTION IN XING.
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.