37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1488285 |
Time | |
Date | 201710 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | BJC.Tower |
State Reference | CO |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Citationjet (C525/C526) - CJ I / II / III / IV |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Amateur/Home Built/Experimental |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | VFR Route |
Person 1 | |
Function | Flight Data / Clearance Delivery Ground |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 8 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft X was inbound on a visual approach with two VFR targets on 1200 codes northbound near east of class D airspace. As aircraft X checked on; I heard the local controller issuing traffic and I believe aircraft X reported traffic in sight. One target was north of the final and no longer a factor; however there was also a second target (aircraft Y) near the final; also northbound around 7300 ft.aircraft X asked what the intentions of the traffic above him were; and the tower controller responded that intentions were unknown because the aircraft (aircraft Y) had not established communications and appeared to be transitioning east of the class D airspace. Aircraft X responded 'not good'. Aircraft Y established communications after that. The transitioning aircraft reported that he was aware of the traffic on final as he transitioned in the VFR corridor; and the tower controller suggested to the transitioning aircraft in the future he may want to communicate with ATC due to the volume of traffic in the area. Aircraft Y acknowledged he would in the future. A mor (mandatory occurrence report) was also filed as a 'public inquiry' due to the concern expressed by aircraft X about proximity of the other traffic. This is one more event highlighting concern about the design of this airspace corridor; where VFR aircraft operate without communication with ATC. In situations like these; such aircraft skirting controlled airspace can create conflicts with aircraft transitioning from approach over to the tower frequency. In fact; in the event of an inoperative transponder; we might not even know such transitioning aircraft were even there! Many of these conflicts could be mitigated and managed better if aircraft operating so close to class B and class D airspace would communicate with ATC; or if controlled airspace was redesigned to ensure aircraft could not operate in this area or at those higher altitudes without first establishing communication with ATC.
Original NASA ASRS Text
Title: BJC Tower Controller reported that an aircraft on visual approach was concerned that an aircraft in a VFR corridor was too close.
Narrative: Aircraft X was inbound on a Visual Approach with two VFR targets on 1200 codes northbound near east of Class D airspace. As Aircraft X checked on; I heard the Local Controller issuing traffic and I believe Aircraft X reported traffic in sight. One target was north of the final and no longer a factor; however there was also a second target (Aircraft Y) near the final; also northbound around 7300 ft.Aircraft X asked what the intentions of the traffic above him were; and the tower controller responded that intentions were unknown because the aircraft (Aircraft Y) had not established communications and appeared to be transitioning east of the Class D airspace. Aircraft X responded 'not good'. Aircraft Y established communications after that. The transitioning aircraft reported that he was aware of the traffic on final as he transitioned in the VFR corridor; and the Tower Controller suggested to the transitioning aircraft in the future he may want to communicate with ATC due to the volume of traffic in the area. Aircraft Y acknowledged he would in the future. A MOR (Mandatory Occurrence Report) was also filed as a 'public inquiry' due to the concern expressed by Aircraft X about proximity of the other traffic. This is one more event highlighting concern about the design of this airspace corridor; where VFR aircraft operate without communication with ATC. In situations like these; such aircraft skirting controlled airspace can create conflicts with aircraft transitioning from Approach over to the Tower frequency. In fact; in the event of an inoperative transponder; we might not even know such transitioning aircraft were even there! Many of these conflicts could be mitigated and managed better if aircraft operating so close to Class B and Class D airspace would communicate with ATC; or if controlled airspace was redesigned to ensure aircraft could not operate in this area or at those higher altitudes without first establishing communication with ATC.
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.