The U.S. aircraft register, updated daily
Accidents · NTSB ERA18FA150 · Final report

Piper PA28 accident near Chesapeake, Virginia, May 22, 2018

On May 22, 2018 at about 11:28 am local time, a 1964 Piper PA28, registered N6177W, was destroyed in an accident during enroute (climb to cruise) near Chesapeake, Virginia (Chesapeake Rgnl airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The pilot's loss of airplane control due to spatial disorientation during the departure climb in instrument meteorological conditions.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
May 22, 2018 · about 11:28 am local time
Place
Chesapeake, Virginia · Chesapeake Rgnl · map
Type
Accident
Injuries
1 person was killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Piper PA28 140, built 1964 · all PA28s on the register
Registration
N6177W · no longer on the register · serial 28-20194
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The commercial pilot completed a normal preflight inspection and engine run-up and received an instrument flight rules clearance from air traffic control to depart from the uncontrolled airport, where fog, low visibility, and clouds were present. Shortly after takeoff, the airplane entered the clouds and fog, climbed on the departure runway heading, and turned right, consistent with the clearance provided; however, the airplane continued the right turn, flying a 360° circle. During the circle, the airplane rapidly descended to about 60 ft above ground level (agl) then climbed to about 600 ft agl. The last radar data point showed the airplane at 356 ft agl, flying at 42 knots groundspeed. There were no communications received from the pilot during the flight. The wreckage was located in an open field about 1/4 mile from the last radar data point. A postaccident examination of the airplane and the airplane's primary vacuum system did not reveal any anomalies consistent with a preimpact failure or malfunction. The airplane was equipped with a standby vacuum system and an electrically-powered attitude indicator, and the investigation found no anomalies with these components. Due to impact and fire damage, the investigation could not determine whether the standby vacuum system was activated by the pilot. The restricted visibility, maneuvering, and workload associated with the initial post-takeoff phase of flight provided conditions conducive to the development of spatial disorientation, and the changes in the airplane's altitude, heading, and speed depicted on radar are consistent with the known effects of spatial disorientation. It is likely that the pilot experienced spatial disorientation during the climbing departure turn, which resulted in an exceedance of the airplane's critical angle of attack, an aerodynamic stall, and a subsequent impact with terrain.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of control in flight during enroute (climb to cruise) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during enroute (climb to cruise)
  3. Fire/smoke (post-impact) during post (impact)

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Personnel issues › Psychological › Perception/orientation/illusion › Spatial disorientation › Pilot
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low ceiling › Contributed to outcome
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low visibility › Contributed to outcome
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Fog › Contributed to outcome

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 2,100 hours in all
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 4,322.4 hours
  • Last inspection: annual inspection, January 12, 2018
  • Maximum gross weight: 2,150 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320-E2A (piston); 1,927 hours total
  • Fire on the ground

The flight

  • Departed from: CPK Chesapeake VA at 11:26 am
  • Destination: FRG Farmingdale NY
  • Flight plan: IFR
  • Runway 23, 5,500 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 070° at 3 knots
  • Visibility: 0.2 statute miles
  • Sky: overcast at 200 ft
  • Temperature: 66°F (19°C), dew point 64°F (18°C)
  • Altimeter: 30.12 inHg
  • Observation at 11:15 am from CPK, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

12 documents, released by the NTSB on August 22, 2019. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.