37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1337254 |
Time | |
Date | 201603 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | PIT.TRACON |
State Reference | PA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 1 Eng Retractable Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Small Aircraft Low Wing 1 Eng Fixed Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Other VOR Approach |
Flight Plan | IFR |
Person 1 | |
Function | Approach Departure |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 13 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
A non FAA tower has recently changed its hours to be closed on sundays. On sunday mornings; there are many aircraft in the immediate vicinity of the airport. Aircraft X called via the rco and was issued his clearance. He stated he was number 3 for departure. I instructed him to hold for release and advise number 1 ready to go. Aircraft X called number 1 and I released him via enter controlled airspace via heading 280. This was done due to the amount of VFR traffic in the pattern. I assumed a 280 heading would get the aircraft out of the local traffic pattern safely and allow for a turn on course to the southeast once aircraft X got above any traffic in the local area. I was coordinating and heard a conflict alert. I looked up to see aircraft X less than a mile behind a VFR target and closing. I issued traffic and then a traffic alert to aircraft X who hadn't check on the frequency. I observed aircraft X turn southeast to avoid the VFR traffic. He checked on and we discussed the fact he had to turn to avoid the VFR aircraft in the pattern. I did not brasher warn the aircraft as I thought his deviation from his assigned heading was for safety. [Later that day]; aircraft Y was conducting an approach. Conflict alert activated on approximately a 3 mile final due to one of several VFR targets in the traffic pattern. I did not issue a safety alert. Aircraft Y was instructed to change to advisory frequency prior to the conflict being observed. I did issue caution numerous VFR targets in the vicinity of the airport to aircraft Y prior to frequency change. There is a high level of traffic in the pattern at this airport especially on sunday morning. The non-federal tower being closed makes no safety sense. This is a recent change in operating hours and was done as a cost saving measure. Study the traffic at the airport and make recommendations to the non-federal provider on hours of operation. This tower should reestablish some sort of sunday hours based on traffic and services required. A study of traffic count should be used to establish these hours.
Original NASA ASRS Text
Title: PIT TRACON Controller reported that BVI Tower; a non-FAA facility; recently changed its hours to be closed on Sundays. The PIT Controller recommended the Tower be open on Sundays due to the high levels of traffic.
Narrative: A Non FAA Tower has recently changed its hours to be closed on Sundays. On Sunday mornings; there are many aircraft in the immediate vicinity of the airport. Aircraft X called via the RCO and was issued his clearance. He stated he was number 3 for departure. I instructed him to hold for release and advise number 1 ready to go. Aircraft X called number 1 and I released him via enter controlled airspace via heading 280. This was done due to the amount of VFR traffic in the pattern. I assumed a 280 heading would get the aircraft out of the local traffic pattern safely and allow for a turn on course to the southeast once Aircraft X got above any traffic in the local area. I was coordinating and heard a Conflict Alert. I looked up to see Aircraft X less than a mile behind a VFR target and closing. I issued traffic and then a traffic alert to Aircraft X who hadn't check on the frequency. I observed Aircraft X turn southeast to avoid the VFR traffic. He checked on and we discussed the fact he had to turn to avoid the VFR aircraft in the pattern. I did not brasher warn the aircraft as I thought his deviation from his assigned heading was for safety. [Later that day]; Aircraft Y was conducting an approach. Conflict Alert activated on approximately a 3 mile final due to one of several VFR targets in the traffic pattern. I did not issue a safety alert. Aircraft Y was instructed to change to advisory frequency prior to the conflict being observed. I did issue caution numerous VFR targets in the vicinity of the airport to Aircraft Y prior to frequency change. There is a high level of traffic in the pattern at this airport especially on Sunday morning. The non-federal tower being closed makes no safety sense. This is a recent change in operating hours and was done as a cost saving measure. Study the traffic at the airport and make recommendations to the Non-Federal provider on hours of operation. This Tower should reestablish some sort of Sunday hours based on traffic and services required. A study of traffic count should be used to establish these hours.
Data retrieved from NASA's ASRS site 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.