The U.S. aircraft register, updated daily
Accidents · NTSB BFO88FA060 · Preliminary: the investigation is not finished

Piper PA-32RT-300T accident near Cambridge, Maryland, June 27, 1988

On June 27, 1988, a Piper PA-32RT-300T, registered N21312, was substantially damaged in an accident near Cambridge, Maryland. It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

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

What the record shows

Date
June 27, 1988
Place
Cambridge, Maryland · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-32RT-300T PA-32RT-30 · all PA-32RT-300Ts on the register
Registration
N21312 · no longer on the register · serial 32R-7887199
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

THE PILOT HAD DEPARTED OCEAN CITY, MD APRX 20 MINUTES AFTER TAKEOFF WHEN NEARING THE CHESAPEAKE BAY AT AN ALT OF 3000 FT MSL, A TOTAL LOSS OF ENGINE POWER WAS EXPERIENCED. THE PLT ATTEMPTED TO RESTART THE ENGINE TO NO AVAIL AND A FORCED LANDING WAS MADE IN A SWAMP NEAR CAMBRIDGE, MD. THE PLT AND PASSENGER WERE AIR-LIFTED FROM THE ACCIDENT SITE BY MILITARY HELICOPTER. THE WRECKAGE WAS LATER AIR-LIFTED FROM THE SITE. THE WRECKAGE WAS PLACED ON A FLAT BED TRAILER AND THE ENGINE WAS TEST RUN. THE ENGINE OPERATED NORMALLY WHEN CHECKED UP TO 2000 RPM. CAUSE OF THE LOSS OF POWER COULD NOT BE DETERMINED.

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

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 515 hours in all; 22 in this make and model; 51 in the last 90 days; 27 in the last 30 days; 456 as pilot in command
  • Medical certificate: Class 3 (valid medical--no waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 1,653 hours
  • Last inspection: annual inspection, June 19, 1987; 85 hours since
  • Maximum gross weight: 3,600 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Lycoming TIO-540-S1AD (piston); 0 hours total

The flight

  • Departed from: N80 Ocean City MD at 11:40 pm
  • Destination: W10 Manassas VA
  • Flight plan: none
  • Runway 0

Weather at the time

  • Light: dusk
  • Visibility: 10 statute miles
  • Sky: scat at 5,000 ft
  • Temperature: 84°F (29°C), dew point 0°F (-18°C)
  • Altimeter: 29.00 inHg

Injuries

FatalSeriousMinorNone
Crew1
Passengers1

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Other NTSB records under N21312 the same tail number, which may have belonged to a different aircraft at the time

1999-12-13MIA00LA049 · accident near Fort Lauderdale, FL · substantial damage · minor injuries
1996-05-17LAX96LA202 · accident near Kernville, CA · substantial damage · no injuries

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.