37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 599324 |
Time | |
Date | 200311 |
Day | Fri |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : uin.airport |
State Reference | IL |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air taxi |
Make Model Name | Jetstream 32 |
Operating Under FAR Part | Part 135 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | J3 Cub |
Flight Phase | landing : roll |
Person 1 | |
Affiliation | company : air taxi |
Function | flight crew : captain oversight : pic |
Qualification | pilot : multi engine pilot : cfi pilot : atp |
Experience | flight time last 90 days : 105 flight time total : 3680 flight time type : 1900 |
ASRS Report | 599324 |
Person 2 | |
Affiliation | company : air taxi |
Function | flight crew : first officer |
Events | |
Anomaly | conflict : nmac non adherence : required legal separation |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | flight crew : took precautionary avoidance action |
Miss Distance | horizontal : 100 vertical : 75 |
Supplementary | |
Problem Areas | Airport Aircraft Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
As we left the gate area, the first officer announced that we were taxiing to runway 22 for takeoff (dictated by performance data at aircraft takeoff weight). As we approached runway 13/31, the first officer announced (via CTAF) our intentions to cross runway 13/31 and requested that any traffic in the pattern or area to please respond. Both the captain's and first officer's seats in this aircraft (as with many other aircraft) offer extremely poor visibility to the outside, opposite their respective seats. For this reason, company policy dictates that both the captain and first officer always check their respective sides for conflicting traffic (while taxiing or in-flight), ground vehicles, obstructions, etc, and state whether it is clear or point out the conflict to the other pilot. I called 'clear left' and the first officer called 'clear right.' we continued for a very short time when the first officer yelled 'stop!' I immediately applied aggressive braking to stop our forward motion as a piper cub passed in front of and above our position -- from right to left. At no time did we hear a position report or any communication from this aircraft. The first officer immediately attempted to contact the other aircraft but there was no response. We then continued on to runway 22 and took off without further incident. Operations at uncontrolled airfields require extreme vigilance by all pilots during any operation on the ground, in the traffic pattern or flying in the vicinity of the airfield. Since there is no controling authority/authorized at such airports, we all know that the responsibility for seeing and avoiding other aircraft rests entirely upon the pilots. Since any runway can be used at any one time, pilots may chose different runways depending on wind direction, training exercises, performance restrs, etc. This fact should alert every pilot that conflicting traffic is very possible and should be expected any time they are operating at an uncontrolled field. Also, it is my opinion that it should be mandatory for all aircraft operating at an uncontrolled field to be equipped with (and its pilot utilize) a 2-WAY radio so that his/her intentions can be communicated to other traffic in the area. The more ways available to help pilots identify other aircraft operating on and around a congested, uncontrolled airport the better.
Original NASA ASRS Text
Title: BAE3200 FLT CREW HAS NEAR MISS WITH AN ACFT LNDG ON THE RWY THEY ARE STARTING TO TAXI ACROSS AT UIN, AN UNCTLED AIRFIELD.
Narrative: AS WE LEFT THE GATE AREA, THE FO ANNOUNCED THAT WE WERE TAXIING TO RWY 22 FOR TKOF (DICTATED BY PERFORMANCE DATA AT ACFT TKOF WT). AS WE APCHED RWY 13/31, THE FO ANNOUNCED (VIA CTAF) OUR INTENTIONS TO CROSS RWY 13/31 AND REQUESTED THAT ANY TFC IN THE PATTERN OR AREA TO PLEASE RESPOND. BOTH THE CAPT'S AND FO'S SEATS IN THIS ACFT (AS WITH MANY OTHER ACFT) OFFER EXTREMELY POOR VISIBILITY TO THE OUTSIDE, OPPOSITE THEIR RESPECTIVE SEATS. FOR THIS REASON, COMPANY POLICY DICTATES THAT BOTH THE CAPT AND FO ALWAYS CHK THEIR RESPECTIVE SIDES FOR CONFLICTING TFC (WHILE TAXIING OR INFLT), GND VEHICLES, OBSTRUCTIONS, ETC, AND STATE WHETHER IT IS CLR OR POINT OUT THE CONFLICT TO THE OTHER PLT. I CALLED 'CLR L' AND THE FO CALLED 'CLR R.' WE CONTINUED FOR A VERY SHORT TIME WHEN THE FO YELLED 'STOP!' I IMMEDIATELY APPLIED AGGRESSIVE BRAKING TO STOP OUR FORWARD MOTION AS A PIPER CUB PASSED IN FRONT OF AND ABOVE OUR POS -- FROM R TO L. AT NO TIME DID WE HEAR A POS RPT OR ANY COM FROM THIS ACFT. THE FO IMMEDIATELY ATTEMPTED TO CONTACT THE OTHER ACFT BUT THERE WAS NO RESPONSE. WE THEN CONTINUED ON TO RWY 22 AND TOOK OFF WITHOUT FURTHER INCIDENT. OPS AT UNCTLED AIRFIELDS REQUIRE EXTREME VIGILANCE BY ALL PLTS DURING ANY OP ON THE GND, IN THE TFC PATTERN OR FLYING IN THE VICINITY OF THE AIRFIELD. SINCE THERE IS NO CTLING AUTH AT SUCH ARPTS, WE ALL KNOW THAT THE RESPONSIBILITY FOR SEEING AND AVOIDING OTHER ACFT RESTS ENTIRELY UPON THE PLTS. SINCE ANY RWY CAN BE USED AT ANY ONE TIME, PLTS MAY CHOSE DIFFERENT RWYS DEPENDING ON WIND DIRECTION, TRAINING EXERCISES, PERFORMANCE RESTRS, ETC. THIS FACT SHOULD ALERT EVERY PLT THAT CONFLICTING TFC IS VERY POSSIBLE AND SHOULD BE EXPECTED ANY TIME THEY ARE OPERATING AT AN UNCTLED FIELD. ALSO, IT IS MY OPINION THAT IT SHOULD BE MANDATORY FOR ALL ACFT OPERATING AT AN UNCTLED FIELD TO BE EQUIPPED WITH (AND ITS PLT UTILIZE) A 2-WAY RADIO SO THAT HIS/HER INTENTIONS CAN BE COMMUNICATED TO OTHER TFC IN THE AREA. THE MORE WAYS AVAILABLE TO HELP PLTS IDENT OTHER ACFT OPERATING ON AND AROUND A CONGESTED, UNCTLED ARPT THE BETTER.
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.