 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Hcf TRACON controller reported an aircraft was on the wrong heading and issued two different headings to correct the aircraft but realized the aircraft was below the MVA.
| Attributes | |
| ACN | 1672874 |
| Time | |
| Date | 201908 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | HNL.Airport |
| State Reference | HI |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | B757-300 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Departure Approach |
| Qualification | Air Traffic Control Developmental |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
I was working local control and I observed aircraft X flying runway heading off of runway 8R about 2 miles off the departure end climbing into rapidly rising terrain. I was distracted by another task that initially I did not notice. Aircraft X wasn't on his correct heading. When I looked out the window; I couldn't see him because he blended in with the city lights and I only realized where he was by looking at the radar. As soon as I noticed he wasn't on his assigned heading of 140 I turned him to a 155. I immediately realized the 155 heading was not enough I continued him to a heading of 180. Although both headings I issued where below the MVA. In order to prevent a recurrence I would recommend making sure the aircraft is doing what they are supposed to be doing by monitoring them closely or telling them to fix the issue quicker. Also if something like this should happen again I should've issued a low altitude alert. I will review my MVA's so I know what heading I should issue to have him stay away from the rapidly rising terrain.
Original NASA ASRS Text
Title: HCF TRACON Controller reported an aircraft was on the wrong heading and issued two different headings to correct the aircraft but realized the aircraft was below the MVA.
Narrative: I was working Local Control and I observed Aircraft X flying runway heading off of Runway 8R about 2 miles off the departure end climbing into rapidly rising terrain. I was distracted by another task that initially I did not notice. Aircraft X wasn't on his correct heading. When I looked out the window; I couldn't see him because he blended in with the city lights and I only realized where he was by looking at the radar. As soon as I noticed he wasn't on his assigned heading of 140 I turned him to a 155. I immediately realized the 155 heading was not enough I continued him to a heading of 180. Although both headings I issued where below the MVA. In order to prevent a recurrence I would recommend making sure the aircraft is doing what they are supposed to be doing by monitoring them closely or telling them to fix the issue quicker. Also if something like this should happen again I should've issued a Low Altitude Alert. I will review my MVA's so I know what heading I should issue to have him stay away from the rapidly rising terrain.
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.