 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Nct TRACON controller reported an airliner had difficulty getting the runway lights on; executed a go-around; and ended up below the MVA.
| Attributes | |
| ACN | 1672873 |
| Time | |
| Date | 201908 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | MRY.Airport |
| State Reference | CA |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | Regional Jet CL65 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7 |
| Events | |
| Anomaly | Inflight Event / Encounter CFTT / CFIT |
Narrative:
Aircraft X flew the ILS 10R at mry. They executed a missed approach because they could not get the runway lights on (the tower was closed). The missed approach is basically a climbing left turn approximately heading 030 to 5;000 feet. The aircraft climbed to 2;800 feet and flew runway heading towards high terrain. They did not check in with me until about 2 miles past the runway end. They were already in a 3;700 feet. MVA heading towards a 5;000 feet MVA. I issued an immediate climb to 6;000 feet; a low altitude alert; and a vector away from terrain. I issued aircraft X the pilot deviation statement; later while they were being sequenced for the ILS.I suspect that the aircrew was behind the aircraft workload the whole time and did not notice the published missed approach. I gave the pilot the CTAF frequency to turn on the lights. So it is odd that they could not turn on the lights. The other aircraft had no issues turning on the lights. They might have been running numbers for landing because the wind slightly favored runway 28; but the ceiling was too low.the pilot should have informed me that they were not 100% ready for the approach. I could have easily accommodated this request and given them ample time to get ready. At the very minimum; an expeditious switch to my frequency during the missed approach could have prevented this.
Original NASA ASRS Text
Title: NCT TRACON Controller reported an airliner had difficulty getting the runway lights on; executed a go-around; and ended up below the MVA.
Narrative: Aircraft X flew the ILS 10R at MRY. They executed a missed approach because they could not get the runway lights on (the Tower was closed). The missed approach is basically a climbing left turn approximately heading 030 to 5;000 feet. The aircraft climbed to 2;800 feet and flew runway heading towards high terrain. They did not check in with me until about 2 miles past the runway end. They were already in a 3;700 feet. MVA heading towards a 5;000 feet MVA. I issued an immediate climb to 6;000 feet; a low altitude alert; and a vector away from terrain. I issued Aircraft X the pilot deviation statement; later while they were being sequenced for the ILS.I suspect that the aircrew was behind the aircraft workload the whole time and did not notice the published missed approach. I gave the pilot the CTAF frequency to turn on the lights. So it is odd that they could not turn on the lights. The other aircraft had no issues turning on the lights. They might have been running numbers for landing because the wind slightly favored Runway 28; but the ceiling was too low.The pilot should have informed me that they were not 100% ready for the approach. I could have easily accommodated this request and given them ample time to get ready. At the very minimum; an expeditious switch to my frequency during the missed approach could have prevented this.
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.