Number 265
September 2001
Operating Safely at Airports Without Control Towers
There are several keys to safe operations at airports that do not have an operating Control Tower. One is selection of the correct Common Traffic Advisory Frequency (CTAF), the frequency designated for carrying out airport advisory practices. The CTAF may be a UNICOM, MULTICOM, FSS, or Tower frequency and is identified in appropriate aeronautical publications. Another crucial practice is careful visual scanning to see and avoid other aircraft, especially those that are low-flying, on straight-in approaches, or have no radios. Recent ASRS reports illustrate several problematic scenarios that can occur at fields without operating Control Towers.
Opposite Direction on the Same Runway
s We were departing [non-tower field] on Runway 05, wind was calm. Made numerous calls that our King Air was taxiing from the ramp to Runway 05, departing Runway 05, etc. [Piper] Archer made no radio calls. We heard other aircraft in pattern using Runway 05. As we were accelerating to V1, the [Piper] Archer came over the hump in the runway. He was using Runway 23. I swerved right and aborted the takeoff. We missed by 30 feet. The fact that the ends of the runway are not visible from one another was a major factor in this occurrence. Also, the fact that the [Piper] Archer made no radio calls is the most important factor. The best way to avoid this problem in the future is for [pilots] to…follow standard established procedures for operating in non-controlled environments.
This could have been a safety hazard if the other aircraft had not made the radio call… Factors affecting the situation: (1) Runway 32 is the preferred runway – we were using Runway 14 for our direction of flight; (2) We wanted to depart promptly to avoid a conflict with the downwind aircraft. The reporter also mentioned that he was the only one monitoring CTAF while his First Officer was getting the clearance from Approach Control, and for this reason the crew might have missed the Cessna’s earlier CTAF calls. Pilots on IFR flight plans, like this crew, also have the option of asking Approach Control whether there is traffic inbound for the runway in use.
No Radio Aircraft
s While taxiing to the end of Runway 03 for takeoff I
checked the runway and traffic pattern. I had no radio so I couldn’t hear the radio traffic. I was checking the runway for traffic and saw none. As I crossed the hold line for Runway 03 I checked again and saw a Cessna 172 bounce after touchdown on the runway. I immediately stopped halfway between the hold line and the edge of the runway. After the C172 turned off the runway and passed me, I back-taxied to Runway 21 and took off… The Cessna apparently blended in with the background of trees and buildings and I did not see the Cessna until it bounced after touching down… The Aeronautical Information Manual section 4-1-9 offers a comprehensive summary of recommended communications procedures at airports without operating control towers, and emphasizes that not all aircraft operating into these fields have radios.
Use of a Non-Preferred Runway
s At XA43 [local time] we reported on CTAF 119.4,
B737 pushing back for departure, Runway 14 [airport]. Tower does not open until XB00 local time. At XA45 we reported B737 taxiing for Runway 14 [airport]. We noticed one aircraft in the pattern for Runway 32 that reported downwind for Runway 32. At XA50 we were released by Approach for departure. We verified the aircraft visually on downwind abeam midfield and reported on CTAF, “B737 departing Runway 14 [airport].” Immediately, we heard on CTAF, “I’m on my takeoff roll, Runway 32.” At the far end of the runway we notice a Cessna on takeoff roll…We delayed our takeoff.
ASRS Recently Issued Alerts On…
Multiple CL65 inflight windshield failures Terrain-related B767 map shift near a Chilean VOR Lack of onboard escorts for passengers deported by INS ‘Hold short’ signage and marking at a West Coast airport Inflight avionics fire/smoke in a single-pilot BE99 operation
A Monthly Safety Bulletin from
The Office of the NASA Aviation Safety Reporting System, P.O. Box 189, Moffett Field, CA 94035-0189 http://asrs.arc.nasa.gov/
April 2001 Report Intake
Air Carrier / Air Taxi Pilots General Aviation Pilots Controllers Cabin/Mechanics/Military/Other TOTAL 2536 829 72 168 3605
飞行翻译公司 www.aviation.cn 本文链接地址：美国ASRS安全公告CALLBACK cb_265.pdf
September 2001
Operating Safely at Airports Without Control Towers
There are several keys to safe operations at airports that do not have an operating Control Tower. One is selection of the correct Common Traffic Advisory Frequency (CTAF), the frequency designated for carrying out airport advisory practices. The CTAF may be a UNICOM, MULTICOM, FSS, or Tower frequency and is identified in appropriate aeronautical publications. Another crucial practice is careful visual scanning to see and avoid other aircraft, especially those that are low-flying, on straight-in approaches, or have no radios. Recent ASRS reports illustrate several problematic scenarios that can occur at fields without operating Control Towers.
Opposite Direction on the Same Runway
s We were departing [non-tower field] on Runway 05, wind was calm. Made numerous calls that our King Air was taxiing from the ramp to Runway 05, departing Runway 05, etc. [Piper] Archer made no radio calls. We heard other aircraft in pattern using Runway 05. As we were accelerating to V1, the [Piper] Archer came over the hump in the runway. He was using Runway 23. I swerved right and aborted the takeoff. We missed by 30 feet. The fact that the ends of the runway are not visible from one another was a major factor in this occurrence. Also, the fact that the [Piper] Archer made no radio calls is the most important factor. The best way to avoid this problem in the future is for [pilots] to…follow standard established procedures for operating in non-controlled environments.
This could have been a safety hazard if the other aircraft had not made the radio call… Factors affecting the situation: (1) Runway 32 is the preferred runway – we were using Runway 14 for our direction of flight; (2) We wanted to depart promptly to avoid a conflict with the downwind aircraft. The reporter also mentioned that he was the only one monitoring CTAF while his First Officer was getting the clearance from Approach Control, and for this reason the crew might have missed the Cessna’s earlier CTAF calls. Pilots on IFR flight plans, like this crew, also have the option of asking Approach Control whether there is traffic inbound for the runway in use.
No Radio Aircraft
s While taxiing to the end of Runway 03 for takeoff I
checked the runway and traffic pattern. I had no radio so I couldn’t hear the radio traffic. I was checking the runway for traffic and saw none. As I crossed the hold line for Runway 03 I checked again and saw a Cessna 172 bounce after touchdown on the runway. I immediately stopped halfway between the hold line and the edge of the runway. After the C172 turned off the runway and passed me, I back-taxied to Runway 21 and took off… The Cessna apparently blended in with the background of trees and buildings and I did not see the Cessna until it bounced after touching down… The Aeronautical Information Manual section 4-1-9 offers a comprehensive summary of recommended communications procedures at airports without operating control towers, and emphasizes that not all aircraft operating into these fields have radios.
Use of a Non-Preferred Runway
s At XA43 [local time] we reported on CTAF 119.4,
B737 pushing back for departure, Runway 14 [airport]. Tower does not open until XB00 local time. At XA45 we reported B737 taxiing for Runway 14 [airport]. We noticed one aircraft in the pattern for Runway 32 that reported downwind for Runway 32. At XA50 we were released by Approach for departure. We verified the aircraft visually on downwind abeam midfield and reported on CTAF, “B737 departing Runway 14 [airport].” Immediately, we heard on CTAF, “I’m on my takeoff roll, Runway 32.” At the far end of the runway we notice a Cessna on takeoff roll…We delayed our takeoff.
ASRS Recently Issued Alerts On…
Multiple CL65 inflight windshield failures Terrain-related B767 map shift near a Chilean VOR Lack of onboard escorts for passengers deported by INS ‘Hold short’ signage and marking at a West Coast airport Inflight avionics fire/smoke in a single-pilot BE99 operation
A Monthly Safety Bulletin from
The Office of the NASA Aviation Safety Reporting System, P.O. Box 189, Moffett Field, CA 94035-0189 http://asrs.arc.nasa.gov/
April 2001 Report Intake
Air Carrier / Air Taxi Pilots General Aviation Pilots Controllers Cabin/Mechanics/Military/Other TOTAL 2536 829 72 168 3605
飞行翻译公司 www.aviation.cn 本文链接地址：美国ASRS安全公告CALLBACK cb_265.pdf
自定义标签： 
