37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1340415 |
Time | |
Date | 201603 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | HCF.TRACON |
State Reference | HI |
Environment | |
Flight Conditions | IMC |
Aircraft 1 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Medium Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Supervisor / CIC Enroute Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 24.5 |
Person 2 | |
Function | Enroute Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 16.0 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
The weather at was IFR. While doing duties at the watch desk as the front line manager (flm); the controller working advised me that they would be holding arrival aircraft; apparently for spacing. I went to the sector to observe the situation and to see if I could offer assistance to the controller. I noticed that there were two aircraft being sequenced to the airport. Aircraft X was 10 miles south of the airport and there was aircraft Y; approximately 20 miles south of the airport. There was another aircraft approximately 25 miles south but that aircraft was being held by the adjacent sector at a higher altitude and was not yet being sequenced and was not being worked by the controller.as I was sorting out what was happening; I heard the controller clear aircraft X for the ILS approach via a 350 heading to intercept the ILS. At this time; aircraft X was level at 3;000 feet. I suspected that this heading may have caused aircraft X to fly through an area with a higher minimum vectoring altitude (MVA)/mia (3;500) and also caused aircraft X to intercept the ILS course inside of the final approach fix. When the controller was relieved from the position; I advised them of the possible situation and advised them that a radar replay was being requested. The radar replay did confirm the MVA/mia violation and the ILS intercept.aircraft X should have been vectored further southwest before being given the 350 heading to intercept the ILS. The aircraft behind was not a factor; or spacing could have been provided if needed.
Original NASA ASRS Text
Title: A Controller vectored an aircraft to an ILS Approach below the MVA (Minimum Vectoring Altitude) and ILS interception inside the Final Approach Fix.
Narrative: The weather at was IFR. While doing duties at the Watch desk as the Front Line Manager (FLM); the Controller working advised me that they would be holding arrival aircraft; apparently for spacing. I went to the sector to observe the situation and to see if I could offer assistance to the Controller. I noticed that there were two aircraft being sequenced to the airport. Aircraft X was 10 miles south of the airport and there was aircraft Y; approximately 20 miles south of the airport. There was another aircraft approximately 25 miles south but that aircraft was being held by the adjacent sector at a higher altitude and was not yet being sequenced and was not being worked by the Controller.As I was sorting out what was happening; I heard the Controller clear Aircraft X for the ILS approach via a 350 Heading to intercept the ILS. At this time; Aircraft X was level at 3;000 feet. I suspected that this heading may have caused Aircraft X to fly through an area with a higher Minimum Vectoring Altitude (MVA)/MIA (3;500) and also caused Aircraft X to intercept the ILS course inside of the final approach fix. When the Controller was relieved from the position; I advised them of the possible situation and advised them that a radar replay was being requested. The radar replay did confirm the MVA/MIA violation and the ILS intercept.Aircraft X should have been vectored further southwest before being given the 350 Heading to intercept the ILS. The aircraft behind was not a factor; or spacing could have been provided if needed.
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.