37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 860033 |
Time | |
Date | 200911 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | MQI.Airport |
State Reference | NC |
Environment | |
Flight Conditions | IMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 135 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural FAR Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence |
Narrative:
We were scheduled to fly a part 135 trip with one passenger to mqi. After studying the weather conditions and conference with the dispatcher on duty and the assistant chief pilot (acp) on duty; I decided that the trip was feasible. We were planned; according to our release; to fly the GPS runway 5 approach at kmqi. On the feasibility page of our brief; there was a note that stated that approaches to runway 5 may not be available due to restricted airspace. In the fdc notams for this airport; there was a note stating that straight-in and circling approaches to runway 23 at night were not available. I overlooked this information and subsequently was not aware that circling approaches were not allowed. When we arrived in the kmqi area; we were notified by ATC that the GPS runway 5 approach was not available due to military restricted airspace. Winds at the airport were approximately 030 at 12 knots gusting to 18 knots; with frequent variation; so a landing on runway 23 was not permissible. I called the acp and the dispatcher on duty; while the sic was flying the aircraft and discussed the situation. I told them of my intention to fly the GPS runway 23 approach and circle to runway 5. I also asked the dispatcher if there were any restrictions to an approach to runway 23; and he said there were none that he was aware of. Since the AWOS at mqi indicated that the airport was above minimums for the circling approach to runway 23; I decided to fly the approach. We requested and received a clearance to fly the GPS runway 23 approach to circle to runway 5 and we flew this approach but flew the missed approach on the downwind to runway 5 due to encountering IMC. We then returned to our departure airport. We were very task saturated during the time period of the approach due to weather and fuel planning considerations. There were also problems with communications to dispatch due to commercial communications system problems. I realize that I should have checked and been aware of the prohibition of flying circling approaches to runway 23 at night as well as the possibility of approaches to runway 5 not being available. In the future; I will be more careful to be aware of all information regarding an airport.
Original NASA ASRS Text
Title: A Fractional Pilot filed to MQI for a night landing but missed the NOTAM indicating Runway 23 approaches were not available at night. The Runway 5 GPS was not available because of military use and after an attempt to circle to land Runway 23 the flight returned to its destination.
Narrative: We were scheduled to fly a part 135 trip with one passenger to MQI. After studying the weather conditions and conference with the Dispatcher on duty and the Assistant Chief Pilot (ACP) on duty; I decided that the trip was feasible. We were planned; according to our release; to fly the GPS Runway 5 approach at KMQI. On the feasibility page of our brief; there was a note that stated that approaches to Runway 5 may not be available due to restricted airspace. In the FDC NOTAMs for this airport; there was a note stating that straight-in and circling approaches to Runway 23 at night were not available. I overlooked this information and subsequently was not aware that circling approaches were not allowed. When we arrived in the KMQI area; we were notified by ATC that the GPS Runway 5 approach was not available due to military restricted airspace. Winds at the airport were approximately 030 at 12 knots gusting to 18 knots; with frequent variation; so a landing on Runway 23 was not permissible. I called the ACP and the Dispatcher on duty; while the SIC was flying the aircraft and discussed the situation. I told them of my intention to fly the GPS Runway 23 approach and circle to Runway 5. I also asked the Dispatcher if there were any restrictions to an approach to Runway 23; and he said there were none that he was aware of. Since the AWOS at MQI indicated that the airport was above minimums for the circling approach to Runway 23; I decided to fly the approach. We requested and received a clearance to fly the GPS Runway 23 approach to circle to Runway 5 and we flew this approach but flew the missed approach on the downwind to Runway 5 due to encountering IMC. We then returned to our departure airport. We were very task saturated during the time period of the approach due to weather and fuel planning considerations. There were also problems with communications to Dispatch due to commercial communications system problems. I realize that I should have checked and been aware of the prohibition of flying circling approaches to Runway 23 at night as well as the possibility of approaches to Runway 5 not being available. In the future; I will be more careful to be aware of all information regarding an airport.
Data retrieved from NASA's ASRS site as of April 2012 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.