37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 519216 |
Time | |
Date | 200107 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : guc.airport |
State Reference | CO |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | Skylane 182/RG Turbo Skylane/RG |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : takeoff ground : position and hold ground : takeoff roll |
Flight Plan | VFR |
Aircraft 2 | |
Operator | common carrier : air taxi |
Make Model Name | Beech 1900 |
Operating Under FAR Part | Part 135 |
Flight Phase | climbout : takeoff ground : takeoff roll |
Flight Plan | IFR |
Person 1 | |
Affiliation | other |
Function | observation : passenger |
ASRS Report | 519216 |
Person 2 | |
Affiliation | other |
Function | instruction : trainee |
Events | |
Anomaly | conflict : ground critical incursion : runway non adherence : far non adherence : published procedure |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : took evasive action |
Miss Distance | horizontal : 3000 vertical : 200 |
Supplementary | |
Problem Areas | Environmental Factor Airport Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Narrative:
Announced intentions to depart runway 6 on CTAF 122.7 prior to taxi to runway 6. Winds at this time favored runway 6 per the nearest windsock and unicom advisory. A turbo commander had just departed ahead of aircraft X on runway 6. While aircraft X taxied to runway 6, an air carrier beechcraft 1900 announced intention (on 122.7) to depart runway 24. Using 122.7, aircraft X called the B1900 to reannounce intention to use runway 6. There was no response from the B1900. Aircraft X then performed its run-up. Aircraft X announced its intention to depart runway 6 and specifically asked the intention and position of the beechcraft. No response was received from the beechcraft. We still heard nothing from the B1900. At that time aircraft X made another call on 122.7 announcing intention to depart runway 6. No other traffic replied. At this time we assumed that the B1900 was off the unicom frequency, probably getting IFR clearance. Since they were unresponsive, we further assumed they were not moving or ready to depart. After stopping at the departure end of runway 6 and doing a high altitude leaning, the brakes were released and aircraft X started its ground roll. Just after beginning its roll, the CFI in the right front seat made the comment that he thought he saw an aircraft departing runway 24. He immediately took control of the aircraft and the left seat pilot immediately released control to the CFI, who initiated an immediate 180 degree turn. The CFI evaluated leaving the runway at that point, however, felt there was sufficient space and time to go the distance back to the taxiway. Aircraft X exited onto the taxiway after a high speed taxi, at the extreme right side of the runway. From the back seat, I was able to watch the B1900 take off, and kept our pilot informed that the B1900 was off the ground well behind us, and was no factor for collision. Immediately upon clearing the runway, the CFI called on 122.7 to the B1900 to notify them of the situation. No response was heard. At about this time I observed the B1900 fly over us at least 200 ft AGL. About 15-20 seconds later, the B1900 made a routine call announcing 'off runway 24 at guc.' there was no indication that the B1900 heard our call to them, or was ever aware of our presence on runway 6. After rechking for conflicting traffic, and making the appropriate calls on 122.7, aircraft X departed runway 6 with no further incidents. Contributing factors: 1) B1900 not monitoring or talking on unicom frequency 122.7. 2) our assumption that the B1900 was not departing since it never communicated with guc traffic. 3) construction on the taxiway, requiring back-taxi on the runway to go to the opposite end. Human performance considerations: 1) commuter pilots being complacent with operations at non twred airports. 2) our assumption that 'airline pilots' would make traffic calls at non twred airports. 3) our assumption that since we didn't hear anything, the B1900 must not be moving.
Original NASA ASRS Text
Title: A C182 INSTRUCTOR, STUDENT, AND PAX STARTED TKOF ROLL AT GUC, A NON TWR ARPT, EVEN THOUGH A LCL COMMUTER HAD ANNOUNCED THEIR INTENTIONS TO USE THE OPPOSITE DIRECTION RWY.
Narrative: ANNOUNCED INTENTIONS TO DEPART RWY 6 ON CTAF 122.7 PRIOR TO TAXI TO RWY 6. WINDS AT THIS TIME FAVORED RWY 6 PER THE NEAREST WINDSOCK AND UNICOM ADVISORY. A TURBO COMMANDER HAD JUST DEPARTED AHEAD OF ACFT X ON RWY 6. WHILE ACFT X TAXIED TO RWY 6, AN ACR BEECHCRAFT 1900 ANNOUNCED INTENTION (ON 122.7) TO DEPART RWY 24. USING 122.7, ACFT X CALLED THE B1900 TO REANNOUNCE INTENTION TO USE RWY 6. THERE WAS NO RESPONSE FROM THE B1900. ACFT X THEN PERFORMED ITS RUN-UP. ACFT X ANNOUNCED ITS INTENTION TO DEPART RWY 6 AND SPECIFICALLY ASKED THE INTENTION AND POS OF THE BEECHCRAFT. NO RESPONSE WAS RECEIVED FROM THE BEECHCRAFT. WE STILL HEARD NOTHING FROM THE B1900. AT THAT TIME ACFT X MADE ANOTHER CALL ON 122.7 ANNOUNCING INTENTION TO DEPART RWY 6. NO OTHER TFC REPLIED. AT THIS TIME WE ASSUMED THAT THE B1900 WAS OFF THE UNICOM FREQ, PROBABLY GETTING IFR CLRNC. SINCE THEY WERE UNRESPONSIVE, WE FURTHER ASSUMED THEY WERE NOT MOVING OR READY TO DEPART. AFTER STOPPING AT THE DEP END OF RWY 6 AND DOING A HIGH ALT LEANING, THE BRAKES WERE RELEASED AND ACFT X STARTED ITS GND ROLL. JUST AFTER BEGINNING ITS ROLL, THE CFI IN THE R FRONT SEAT MADE THE COMMENT THAT HE THOUGHT HE SAW AN ACFT DEPARTING RWY 24. HE IMMEDIATELY TOOK CTL OF THE ACFT AND THE L SEAT PLT IMMEDIATELY RELEASED CTL TO THE CFI, WHO INITIATED AN IMMEDIATE 180 DEG TURN. THE CFI EVALUATED LEAVING THE RWY AT THAT POINT, HOWEVER, FELT THERE WAS SUFFICIENT SPACE AND TIME TO GO THE DISTANCE BACK TO THE TXWY. ACFT X EXITED ONTO THE TXWY AFTER A HIGH SPD TAXI, AT THE EXTREME R SIDE OF THE RWY. FROM THE BACK SEAT, I WAS ABLE TO WATCH THE B1900 TAKE OFF, AND KEPT OUR PLT INFORMED THAT THE B1900 WAS OFF THE GND WELL BEHIND US, AND WAS NO FACTOR FOR COLLISION. IMMEDIATELY UPON CLRING THE RWY, THE CFI CALLED ON 122.7 TO THE B1900 TO NOTIFY THEM OF THE SIT. NO RESPONSE WAS HEARD. AT ABOUT THIS TIME I OBSERVED THE B1900 FLY OVER US AT LEAST 200 FT AGL. ABOUT 15-20 SECONDS LATER, THE B1900 MADE A ROUTINE CALL ANNOUNCING 'OFF RWY 24 AT GUC.' THERE WAS NO INDICATION THAT THE B1900 HEARD OUR CALL TO THEM, OR WAS EVER AWARE OF OUR PRESENCE ON RWY 6. AFTER RECHKING FOR CONFLICTING TFC, AND MAKING THE APPROPRIATE CALLS ON 122.7, ACFT X DEPARTED RWY 6 WITH NO FURTHER INCIDENTS. CONTRIBUTING FACTORS: 1) B1900 NOT MONITORING OR TALKING ON UNICOM FREQ 122.7. 2) OUR ASSUMPTION THAT THE B1900 WAS NOT DEPARTING SINCE IT NEVER COMMUNICATED WITH GUC TFC. 3) CONSTRUCTION ON THE TXWY, REQUIRING BACK-TAXI ON THE RWY TO GO TO THE OPPOSITE END. HUMAN PERFORMANCE CONSIDERATIONS: 1) COMMUTER PLTS BEING COMPLACENT WITH OPS AT NON TWRED ARPTS. 2) OUR ASSUMPTION THAT 'AIRLINE PLTS' WOULD MAKE TFC CALLS AT NON TWRED ARPTS. 3) OUR ASSUMPTION THAT SINCE WE DIDN'T HEAR ANYTHING, THE B1900 MUST NOT BE MOVING.
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.