37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1291082 |
Time | |
Date | 201508 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | N90.TRACON |
State Reference | NY |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | EMB ERJ 170/175 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | VFR Route |
Flight Plan | VFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (mon) 18 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance |
Miss Distance | Horizontal 3000 Vertical 0 |
Narrative:
I was working final approach into airport ZZZ landing ILS xx departing runway yy. Airport ZZZ1 was departing runway zz. Aircraft X was set up for right traffic to ILS runway xx at 3;000. Aircraft Y VFR was pointed out at 4;500 feet. Normally VFR aircraft are sent under the class bravo airspace on this runway configuration at 2;500 feet. There was a controller change on the position working aircraft Y; the new controller told aircraft Y to descend out of the bravo and proceed on course. Aircraft Y went on course and started a descent. His on course heading cut off the downwind aircraft X was on; and the planes met at 3;000 and about 0.5 miles in the class bravo airspace. I called traffic and aircraft X never reported aircraft Y in sight. I was unaware at the time of what aircraft Y was doing; I only saw him descending into my traffic.I suggest the VFR aircraft be kept outside of the class bravo and also airport ZZZ1 class D be changed to a class C and extended out to remove these VFR cut through flights away from airport ZZZ and airport ZZZ1 IFR traffic patterns.
Original NASA ASRS Text
Title: Controller approved a point out of VFR traffic at 4;500 feet. The VFR aircraft was on a converging course with an aircraft at 3;000 feet being vectored for an ILS approach. The Controller working the VFR aircraft instructed it to descend and proceed on course. The descent put the VFR aircraft in to confliction with the 3;000 foot traffic.
Narrative: I was working Final approach into Airport ZZZ landing ILS XX departing Runway YY. Airport ZZZ1 was departing Runway ZZ. Aircraft X was set up for right traffic to ILS Runway XX at 3;000. Aircraft Y VFR was pointed out at 4;500 feet. Normally VFR aircraft are sent under the Class Bravo airspace on this runway configuration at 2;500 feet. There was a controller change on the position working Aircraft Y; the new controller told Aircraft Y to descend out of the Bravo and proceed on course. Aircraft Y went on course and started a descent. His on course heading cut off the downwind Aircraft X was on; and the planes met at 3;000 and about 0.5 miles in the Class Bravo airspace. I called traffic and Aircraft X never reported Aircraft Y in sight. I was unaware at the time of what Aircraft Y was doing; I only saw him descending into my traffic.I suggest the VFR aircraft be kept outside of the Class BRAVO and also Airport ZZZ1 Class D be changed to a Class C and extended out to remove these VFR cut through flights away from Airport ZZZ and Airport ZZZ1 IFR traffic patterns.
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.