37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 175852 |
Time | |
Date | 199104 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : m42 |
State Reference | MS |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zoa |
Operator | general aviation : corporate |
Make Model Name | Small Transport, Low Wing, 2 Turbojet Eng |
Navigation In Use | Other |
Flight Phase | ground other : taxi |
Flight Plan | IFR |
Aircraft 2 | |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, High Wing, 1 Eng, Fixed Gear |
Flight Phase | landing other |
Person 1 | |
Affiliation | Other |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 100 flight time total : 11500 flight time type : 4200 |
ASRS Report | 175852 |
Person 2 | |
Affiliation | Other |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | conflict : ground critical incursion : runway |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : took evasive action other |
Consequence | Other |
Miss Distance | horizontal : 50 vertical : 200 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Our aircraft, an small aircraft, was taxiing for departure on runway 22? There was some confusion between myself and the PF as to which runway we were going to use, either 22 or 31. The surface winds at the time were calm. As we passed the taxiway leading to runway 22, I again asked which runway are you going to use? After passing the one for runway 22, he told me that I should have told him sooner. We continued on the taxiway which intersected runway 22 at approximately 40 degree and made viewing the approach end of 22 more difficult. I made a traffic call on unicom (122.8) before entering the runway. We had no response! Upon entering the runway and turning to the approach end, we both saw what appeared to be an small aircraft on low and short final at a distance of approximately 1/2 to 3/4 mi from our aircraft. Due to construction on the airport, we were unable to exit the runway west/O a 180 degree turn. Time and distance would not permit us to clear before the small aircraft landed. The small aircraft took evasive action in the form of a go around. An attempt to contact the small aircraft pilot was unsuccessful.
Original NASA ASRS Text
Title: CORP ACFT TAXIES ONTO ACTIVE RWY AS SMA ON FINAL. SMA DOES GAR.
Narrative: OUR ACFT, AN SMA, WAS TAXIING FOR DEP ON RWY 22? THERE WAS SOME CONFUSION BTWN MYSELF AND THE PF AS TO WHICH RWY WE WERE GOING TO USE, EITHER 22 OR 31. THE SURFACE WINDS AT THE TIME WERE CALM. AS WE PASSED THE TXWY LEADING TO RWY 22, I AGAIN ASKED WHICH RWY ARE YOU GOING TO USE? AFTER PASSING THE ONE FOR RWY 22, HE TOLD ME THAT I SHOULD HAVE TOLD HIM SOONER. WE CONTINUED ON THE TXWY WHICH INTERSECTED RWY 22 AT APPROX 40 DEG AND MADE VIEWING THE APCH END OF 22 MORE DIFFICULT. I MADE A TFC CALL ON UNICOM (122.8) BEFORE ENTERING THE RWY. WE HAD NO RESPONSE! UPON ENTERING THE RWY AND TURNING TO THE APCH END, WE BOTH SAW WHAT APPEARED TO BE AN SMA ON LOW AND SHORT FINAL AT A DISTANCE OF APPROX 1/2 TO 3/4 MI FROM OUR ACFT. DUE TO CONSTRUCTION ON THE ARPT, WE WERE UNABLE TO EXIT THE RWY W/O A 180 DEG TURN. TIME AND DISTANCE WOULD NOT PERMIT US TO CLR BEFORE THE SMA LANDED. THE SMA TOOK EVASIVE ACTION IN THE FORM OF A GO AROUND. AN ATTEMPT TO CONTACT THE SMA PLT WAS UNSUCCESSFUL.
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.