C172 pilots reported the engine quit in cruise when the Pilot Flying turned the fuel selector to off. Flight crew diverted to the closest airport.

Date: 2025-01 · Aircraft: Skyhawk 172/Cutlass 172 · Phase: cruise

Anomalies: aircraft-equipment-problem-critical|deviation-discrepancy-procedural-published-material-policy|inflight-event-encounter-fuel-issue

Synopsis

C172 pilots reported the engine quit in cruise when the Pilot Flying turned the fuel selector to off. Flight crew diverted to the closest airport.

Narrative

Myself and another pilot briefed and planned a 3 leg training flight from ZZZ-ZZZ1-ZZZ2-ZZZ. We departed around XA:00 and landed in ZZZ1 where we refueled and immediately departed for ZZZ2. After a stop for lunch at ZZZ2; we departed for ZZZ. I was the pilot flying the first 2 legs(under the hood) with the other pilot acting as safety pilot. We had flight following for both legs. We switched seats and I was acting as safety pilot for the last leg. During the last leg; we picked up flight following over ZZZ3 for the remainder of the flight. Our tanks had been burning uneven; so we selected the left or right tank and ran it alone for some time. About 30-40nm out from ZZZ we determined the tanks were even and the pilot flying switched the tanks to both. At this point it is night and completely dark in the cockpit; except for the instrument panel. This is where the mistake was made and the pilot flying accidentally switched the fuel selector to off; but we didn't realize at the time. We should have verified. This was an older Cessna with the fuel selector having a right; left; both; and off selection. Roughly 10 minutes passed by and we noticed an rpm drop; we immediately applied full rich mixture and carb heat; but to no avail. The engine quit seconds later and I unfortunately lost my flashlight in the tense situation. We pitched for best glide and immediately turned directly to ZZZ4; which we luckily already had in sight. We were cruising at 3500msl and the airport was only about 3nm away. We contacted ATC with a [request for priority handling] and stated our intentions that we were landing at ZZZ4 immediately. We tried to restart the engine; but with no success. We entered the left downwind for runway XX at ZZZ4 and conducted a power off 180 and landed without incident. I immediately noticed our very stupid mistake on the runway and got the engine restarted and taxied off. We performed a normal run up and pre takeoff checklist and the aircraft was operating normally. We departed for ZZZ where we notified ATC in the air that we were okay and explained the issue; and landed shortly after.Takeaways. No amount of training can prepare you for the stress of having an engine quit on you; especially at night; at a relatively low altitude with only a couple minutes of glide time. But it's very important to remember your training and go through the emergency checklist properly. I assumed we badly mismanaged our fuel supply and maybe had faulty fuel gauges and ran out; but if either of us checked the fuel selector we likely could have restarted the aircraft in the air. Also; I could have explained the situation better to ATC and I missed squawking XXXX and copying the phone number they wanted to provide to call once we we on the ground. However; first aviate; navigate; then communicate. Thankfully we landed safety with no damage to the aircraft or injury. In the future; I will definitely cruise at higher altitudes at night to allow for more time to process the situation in the event of an emergency and will never forget to verify the fuel selector.

Second reporter narrative

I was the pilot in command flying under the hood flying with a safety pilot cruising at 3;500 MSL heading back to ZZZ from ZZZ2. During the flight back to ZZZ we were alternating back and forth which fuel tank to use. Around 35 nm out from ZZZ and about 3 nm from ZZZ4 we went to switch the fuel selector back to both for the remainder of the flight. When the fuel selector was getting switched back to both; it was accidently switched to the off position was it not noticed until after we had safely landed down at ZZZ4. After a safe landing on the runway; the issue to what caused the emergency landing was identified and we were about to safely take back off and make it back to ZZZ.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.