Date: 201901
Local time of day: 1801-2400
Location: DVL.Airport, ND
Flight conditions: VMC
Light: Night
Aircraft: Commercial Fixed Wing
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class E DVL
ATC / advisory: CTAF DVL
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Workload; Communication Breakdown
Second reporter function: First Officer; Pilot Flying
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airport; Human Factors
Primary problem: Airport

Narrative: While on approach to DVL at approximately 3 mile final; the runway lights went out. We initiated a go-around; and started discussing options for where to go. Before we left the frequency; an ops vehicle called us on CTAF and informed us that they'd been having issues with the lights; and they would probably come back on in about 5 minutes. After verifying that we had enough fuel to fly to another airport if we made another attempt; we made a VFR pattern. As we turned base; the ops vehicle contacted us stating the lights were on again. We verified they were; and made a normal landing. While on final the 2nd time; [another] flight overhead tried to contact us; presumably because Center was looking for us as we had not yet canceled. They called us with the wrong call sign; but mentioned DVL airport and CTAF frequency; so I responded that we were on final and would contact Center shortly. They apparently didn't hear me; because they tried to call again. At that point we were focused on landing; so I didn't respond. After landing; we contacted Flight Service to cancel. They indicated no issues. I also called our dispatcher to alert her of the lighting issue at DVL; and she said she had not been contacted by anyone searching for us. The vehicle on the ground at DVL said they had been having issues. They didn't specify; and I didn't ask; for how long the problem had been happening. Our failure to notify ATC of our go-around was due to prioritizing aviate; navigate; communicate. We flew the traffic pattern first. While we did this; we were considering options for where to go if the lights did not re-illuminate; attempting to get more information from the ops vehicle; which was unresponsive; as well as making sure fuel was sufficient to get to another airport. By the time we could have made contact with ATC; we were about to turn our base leg; so aviate once again took priority. Determine the frequency this has been occurring at DVL by contacting airport ops. Provide extra contingency fuel for flights into DVL until the issue is resolved (I suggested this to our dispatcher already; who said she will pass it to the supervisor). If a go-around is necessary; attempt to contact ATC even if your plan is not certain yet. Details can be given and a plan can be made later.


Second narrative: We were cleared for the Visual 13 into Devils Lake; North Dakota. Conditions were night time with good visibility. We switched to the CTAF local frequency and make a normal visual approach. On short final; the runway lights went out and we were unable to reactivate them. A go-around was necessary and we executed a go-around immediately. Captain began to speak with maintenance personnel on the ground and the maintenance person said that it was an ongoing issue but they should come back on shortly. We stayed in the pattern to wait for the lights to come up and we were discussing a contingency plan if the lights would not come up. Another airborne aircraft was attempting to reach us to relay for ATC inquiry but since we were on short final on our second attempt; we did not answer him. On downwind for Runway 13 the lights came back on and we landed without incident. We contacted radio on the ground to cancel our flight plan which we did after landing and no further communication was made with ATC. On our debrief; Captain said we should have contacted ATC after our go-around but because of communication with personnel on the ground and communicating between Captain and First Officer about contingency plans and fuel concerns; we forgot and failed to contact Center regarding the go-around and intentions. Cause: task saturation after runway lights going out on short final. Suggestion: communication with ATC as soon as practicable after a go-around.


Synopsis: Air carier flight crew reported the runway lights at DVL were intermittently unavailable.