Casualties unknown

Night VFR Accident Involving Poor Visibility and Low Experience (N5944E)

Ocean City, MD, US

On June 22, 1998, a Cessna 172N (registration N5944E) was involved in an aviation accident near Ocean City, MD. Investigators recorded the probable cause as: The pilot's failure to maintain control of the aircraft due to spatial disorientation. Contributing factors wer fog, dark night conditions, lack of recent experience, inadequate preflight planning, and flight into known adverse weather. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive; 1 related events involving the same aircraft type or operator are linked below.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 2026-09-03Data APIEditorial standards

A pilot conducting night currency flights in heavy mist and fog lost control during a go-around. The aircraft impacted near the airport, and wreckage was found after 1 hour and 20 minutes due to fog.

Accident Overview and Weather Conditions The pilot had planned to conduct three takeoffs and landings to maintain night currency. No flight plan was filed, and the pilot did not request a weather briefing from Flight Service. At the time of takeoff, visibility was poor due to heavy mist. A witness reported that visibility deteriorated further when a wall of fog covered the airfield while the aircraft was in the traffic pattern. ## Witness Account and Impact The witness heard the aircraft at full power and observed it flying approximately 100 feet over the hangars, with the landing gear illuminated by the rotating beacon. The witness stated that the pilot throttled up to perform a go-around. The witness continued to hear the aircraft until impact. ## Post-Accident Findings Emergency crews from four municipalities required 1 hour and 20 minutes to locate the wreckage on the airport due to heavy fog. The airspeed indicator needle was found crushed against the face at the 160-knot striation. The engine tachometer needle was crushed at the 3,200 RPM striation, which was 500 RPM above the placarded redline. ## Pilot Experience A review of the pilot's logbook showed 135 hours of total flight experience. The pilot had logged 1.8 hours in the month before the accident. Prior to that, the pilot had not flown for 7 months, and the last night experience was 18 months before the accident. The pilot was not instrument rated.

All Cessna 172 accidents →

Frequently asked questions

What happened in the 22 Jun 1998 Cessna 172N accident near Ocean City, MD?

A pilot conducting night currency flights in heavy mist and fog lost control during a go-around. The aircraft impacted near the airport, and wreckage was found after 1 hour and 20 minutes due to fog.

What aircraft was involved and where did it happen?

The accident on 22 Jun 1998 involved a Cessna 172N, registration N5944E, at Ocean City, MD.

What was the probable cause of the accident?

The pilot's failure to maintain control of the aircraft due to spatial disorientation. Contributing factors wer fog, dark night conditions, lack of recent experience, inadequate preflight planning, and flight into known adverse weather.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20001211X10330. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.