37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1388782 |
Time | |
Date | 201609 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | MKG.Airport |
State Reference | MI |
Aircraft 1 | |
Make Model Name | Challenger 300 |
Operating Under FAR Part | Part 135 |
Flight Phase | Landing |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Instructor Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 6 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Ground Incursion Runway |
Narrative:
Myself and developmental received a briefing for the local control position. We were informed of the current traffic situation and informed that the runway (6/24) and taxiway (a; G; H) closures were no longer pertinent as of the closure end times as posted on the system atlanta. Aircraft X was inbound southwest of the field and [the developmental] noticed the winds were more aligned with 24 so he then coordinated with radar for a left downwind entry for the visual approach runway 24 for aircraft X. The aircraft was switched to [the developmental] and cleared to land and landed without incident at which time the phone rang with the county personnel calling asking if an aircraft had landed runway 24 because it was closed. Also of note there were no obstructions or lights of any sort indicating that the runway was closed.the situation in my opinion happened due to incorrect posting of NOTAM information on our systems atlanta page.
Original NASA ASRS Text
Title: MKG Tower Controller/Instructor reported of an instance where an aircraft landed on a NOTAM Closed runway. Reporter did not show the runway closed and was briefed that the runway/taxiway closures were not pertinent.
Narrative: Myself and developmental received a briefing for the Local Control position. We were informed of the current traffic situation and informed that the runway (6/24) and taxiway (A; G; H) closures were no longer pertinent as of the closure end times as posted on the System Atlanta. Aircraft X was inbound southwest of the field and [the developmental] noticed the winds were more aligned with 24 so he then coordinated with radar for a left downwind entry for the visual approach runway 24 for Aircraft X. The aircraft was switched to [the developmental] and cleared to land and landed without incident at which time the phone rang with the county personnel calling asking if an aircraft had landed runway 24 because it was closed. Also of note there were no obstructions or lights of any sort indicating that the runway was closed.The situation in my opinion happened due to incorrect posting of NOTAM information on our Systems Atlanta page.
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.