37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1343626 |
Time | |
Date | 201603 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | N90.TRACON |
State Reference | NY |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Medium Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Small Transport |
Flight Phase | Initial Climb |
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 (yrs) 2.2 |
Events | |
Anomaly | ATC Issue All Types Conflict NMAC Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Hpn ILS16 lga ILS22Aircraft X; IFR; standard at 4;000 on localizer for ILS22. Aircraft Y; VFR; departure off hpn eastbound climbed through aircraft X. Aircraft Y checked in on my frequency at 3;500 before radar identifying him I advised he stopped his climb to avoid collision. Aircraft Y pilot advised aircraft X in sight and turned to avoid. Another near mid air collision from hpn tower with a VFR to IFR.hpn tower provides zero assistance to avoid IFR arrivals east of their airport and switches 1200 code VFR departures from their class D to N90 approach. A change in hpn class of airspace is necessary to avoid this situation; it happens constantly and is a major problem. This is the first and I am sure it isn't that last report that I will have to fill out with the same issue.another suggestion is that hpn inputs into the national airspace system (NAS) every VFR flight plan for their VFR departures and instructs the pilots to maintain 2;500 until advised by approach. 90% of the VFR departures from hpn call N90 for advisories there is no reason they shouldn't get a code from hpn tower. This will help insure positive separation with IFR aircraft landing at both hpn and lga.
Original NASA ASRS Text
Title: N90 TRACON Controller reported of a Near Mid Air Collision. The reporter stated this was the fault of the Tower not advising departing traffic of IFR traffic in their flight path. Reporter would like a change in the HPN airspace and better procedures for the HPN controllers to follow.
Narrative: HPN ILS16 LGA ILS22Aircraft X; IFR; standard at 4;000 on localizer for ILS22. Aircraft Y; VFR; departure off HPN eastbound climbed through Aircraft X. Aircraft Y checked in on my frequency at 3;500 before radar identifying him I advised he stopped his climb to avoid collision. Aircraft Y pilot advised Aircraft X in sight and turned to avoid. Another Near Mid Air Collision from HPN Tower with a VFR to IFR.HPN Tower provides zero assistance to avoid IFR arrivals east of their airport and switches 1200 code VFR departures from their Class D to N90 approach. A change in HPN class of airspace is necessary to avoid this situation; it happens constantly and is a major problem. This is the first and I am sure it isn't that last report that I will have to fill out with the same issue.Another suggestion is that HPN inputs into the National Airspace System (NAS) every VFR flight plan for their VFR departures and instructs the pilots to maintain 2;500 until advised by approach. 90% of the VFR departures from HPN call N90 for advisories there is no reason they shouldn't get a code from HPN Tower. This will help insure positive separation with IFR aircraft landing at both HPN and LGA.
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.