 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Jax TRACON controller reported an airborne conflict between and IFR carrier and a VFR aircraft inbound to fhb. Reporter also requested some type of airspace change over the fhb airport
| Attributes | |
| ACN | 1722209 |
| Time | |
| Date | 202001 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | JAX.TRACON |
| State Reference | FL |
| Aircraft 1 | |
| Make Model Name | B737 Next Generation Undifferentiated |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | Climb |
| Flight Plan | None |
| Person 1 | |
| Function | Trainee |
| Qualification | Air Traffic Control Developmental |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Aircraft X was on a vector towards the jax runway 08 downwind; to miss coastal traffic (as is the norm). I amended the assigned altitude for southbound VFR traffic that I noticed at 047 in a climb. I couldn't turn aircraft X towards the field due to northbound IFR traffic at 050; or left due to adjacent center airspace. My attention was diverted for other duties momentarily; when I noticed the VFR aircraft still in a climb. I issued a right turn heading 040 to aircraft X to pass behind the traffic; but it was too late. I issued another traffic call; and aircraft X responded to a resolution advisory in the turn. Aircraft X was able to accept vectors shortly thereafter to avoid the IFR traffic at 050; and continue the descent.it is only a matter of time before a loss of human life occurs over fhb airport or the coastline east of jax. There is far too much VFR traffic to dodge with air carriers. It's just that simple.there needs to be a class C extension; a class B implemented; or a tower with a class D at fhb that extends over the ocean. It might also work to swap the arrival and departure gates (lunni and crosb) to the ZJX 53/54 (ssi/jkl) sectors. There needs to be a systemic review of this airspace - it isn't safe.
Original NASA ASRS Text
Title: JAX TRACON Controller reported an airborne conflict between and IFR carrier and a VFR aircraft inbound to FHB. Reporter also requested some type of airspace change over the FHB airport
Narrative: Aircraft X was on a vector towards the JAX Runway 08 downwind; to miss coastal traffic (as is the norm). I amended the assigned altitude for southbound VFR traffic that I noticed at 047 in a climb. I couldn't turn Aircraft X towards the field due to Northbound IFR traffic at 050; or left due to adjacent center airspace. My attention was diverted for other duties momentarily; when I noticed the VFR aircraft still in a climb. I issued a right turn heading 040 to Aircraft X to pass behind the traffic; but it was too late. I issued another traffic call; and Aircraft X responded to a resolution advisory in the turn. Aircraft X was able to accept vectors shortly thereafter to avoid the IFR traffic at 050; and continue the descent.It is only a matter of time before a loss of human life occurs over FHB airport or the coastline east of JAX. There is far too much VFR traffic to dodge with air carriers. It's just that simple.There needs to be a Class C extension; a Class B implemented; or a tower with a Class D at FHB that extends over the ocean. It might also work to swap the arrival and departure gates (LUNNI and CROSB) to the ZJX 53/54 (SSI/JKL) sectors. There needs to be a systemic review of this airspace - it isn't safe.
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.