PC-12
Communication Breakdown
Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Flight Crew Executed Go Around / Missed Approach
Airport; Procedure
During a night approach in Aircraft X at ACK in the early morning hours; while the Control Tower was closed; a series of events led to a situation where the aircraft flew over a closed runway with men and equipment on the runway. The Captain and Pilot Flying (PF); First Officer (FO) and the Pilot Monitoring (PM). Entering the right base for runway 24 at ACK; the First Officer keyed the pilot controlled lighting for the airfield. Upon rolling out on a 3 mile final both the PF and the PM immediately recognized the runway edge lights for the runway were not lit. However; the Approach Lighting System and Runway Threshold and End Lights were illuminated. Suspecting the runway was closed; the crew continuing on final as both PF and PM scanned the runway looking for identification that it was closed or unusable. At 1.5 - 2 DME from I-ACK; despite being unable to find a red X or other identification the runway was closed or unusable; the PF initiated a go around at 900ft AGL. While on the go around the aircraft was sidestepped to the right of the runway and no men or equipment were overflown. During this maneuver; ground personnel contacted the crew via radio on the CTAF frequency and informed them that Runway 6/24 was closed but 15/33 was open. The crew acknowledged this and continued on the upwind for runway 24. When traffic pattern altitude was reached; a turn to the left downwind for runway 33 was made; and the aircraft made an uneventful landing on Runway 33. After landing the crew taxied off the runway to the apron and deplaned passengers without incident. We spoke to a line man about not being able to see a red X on the runway. The lineman made a comment that the X's were supposed to be deployed; but to his knowledge they had not been. 1. The flight crew should double check the NOTAMs prior to flight. 2. The airport should deactivate all lighting systems for a closed runway. 3. The airport should ensure that the red X runway closure indicators are in place and operational prior to beginning work on a closed runway.
I was the First Officer (FO) and the Pilot Monitoring (PM) [on Aircraft X]; flying a night approach to ACK while the Control Tower was closed. The Captain and Pilot Flying (PF) entered the right base for runway 24 at ACK. I keyed the pilot controlled lighting for the airfield on the CTAF frequency. We rolled out on final we could see that runway edge lights for the runway were not illuminated. But the Approach Lighting System; Runway Threshold; and Runway End Identifier Lights (REIL) were on. We continued on final; looking for signs that the runway was closed. At about two mile final; the PF initiated a go around. He offset to the right side of the runway. During the go-around; ground personnel contacted us the CTAF frequency and informed them that Runway 6/24 was closed but 15/33 was open. We acknowledged and entered downwind for runway 33. We made an uneventful landing on Runway 33. After landing; we spoke to a lineman about not being able to see a red X on the runway. He said that the X's were supposed to be deployed; but to his knowledge they had not been. 1. During late night flights; you should be aware that airport authorities often perform maintenance on runways and be alert for non-standard operations. 2. The airport authorities should deactivate all lighting systems for a closed runway; not just the runway edge lights. 3. The airport authorities should also ensure that the red X runway closure indicators are in place and operational prior to beginning work on a closed runway.
PC12 flight crew reported closed runway was improperly marked at ACK.