 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Hcf controller reported an airborne conflict between an IFR departure and a VFR aircraft.
| Attributes | |
| ACN | 1466524 |
| Time | |
| Date | 201707 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | HCF.TRACON |
| State Reference | HI |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Small Transport |
| Operating Under FAR Part | Part 135 |
| Flight Phase | Initial Approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Small Transport |
| Operating Under FAR Part | Part 135 |
| Flight Phase | Climb |
| Route In Use | None |
| Flight Plan | VFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
Aircraft X was on the instrument approach into jhm. The aircraft before him reported BKN048 10 northwest of the airport. Aircraft X was 15 northwest of jhm descending when a VFR aircraft on a 1200 squawk departed jhm head on. I issued traffic advisories to aircraft X but had no idea who the other aircraft was. Traffic advisories became traffic alerts 5 miles between the two aircraft at 4800 (same altitude). Then at two miles at 4800 the captain says 'I'm going right'. A right turn would have put the aircraft X even closer and the targets would have merged. I told the aircraft X to make a left 360 before proceeding back on course; they were below the MVA at the time but over water. I noticed aircraft X had climbed to 5000 and asked if they had an RA. The pilot replied in the affirmative and I reported it to my supervisor. Later we found out the other aircraft was aircraft Y when they requested flight following from the adjacent sector. Recommendations:1. Request flight following in and out of jhm.2. Jhm issues a VFR code on the ground and has them contact hcf on departure.3. Development of a VFR procedure where aircraft remain clear of the final approach course.
Original NASA ASRS Text
Title: HCF Controller reported an airborne conflict between an IFR departure and a VFR aircraft.
Narrative: Aircraft X was on the instrument approach into JHM. The Aircraft before him reported BKN048 10 NW of the airport. Aircraft X was 15 NW of JHM descending when a VFR aircraft on a 1200 squawk departed JHM head on. I issued traffic advisories to Aircraft X but had no idea who the other aircraft was. Traffic advisories became traffic alerts 5 miles between the two aircraft at 4800 (same ALT). Then at two miles at 4800 the Captain says 'I'm going right'. A right turn would have put the Aircraft X even closer and the targets would have merged. I told the Aircraft X to make a left 360 before proceeding back on course; they were below the MVA at the time but over water. I noticed Aircraft X had climbed to 5000 and asked if they had an RA. The pilot replied in the affirmative and I reported it to my Supervisor. Later we found out the other aircraft was Aircraft Y when they requested flight following from the adjacent sector. Recommendations:1. Request flight following in and out of JHM.2. JHM issues a VFR code on the ground and has them contact HCF on departure.3. Development of a VFR procedure where aircraft remain clear of the final approach course.
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.