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

Cessna 172P accident near St. Augustine, Florida, July 18, 2012

On July 18, 2012 at about 5:00 pm local time, a Cessna 172P, registered N127EP, was substantially damaged in an accident near St. Augustine, Florida (Unknown airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

Undetermined due to a lack of information about when the damage to the airplane occurred.

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

What the record shows

Date
July 18, 2012 · about 5:00 pm local time · cases in 2012
Place
St. Augustine, Florida · Unknown · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172P · all 172Ps on the register
Registration
N127EP · registry record · serial 17276481
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

During a scheduled 100-hour inspection, maintenance personnel discovered structural damage to the airplane’s firewall. According to the flight school’s records, the airplane had been flown 91.4 hours on 77 flights between the time of the previous 100 hour inspection and the time when the damage was discovered. The flight school was never notified of an event that would have possibly caused the firewall damage. Therefore, the actual time and date and the circumstances of the accident 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

What happened, in order

  1. Unknown or undetermined during unknown defining event

The NTSB's findings

  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined

Pilot

  • Flight time: 0 hours in all; 0 in this make and model
  • Medical certificate: Unknown

The aircraft

  • Airframe total time: 15,266 hours
  • Last inspection: 100-hour inspection, May 8, 2012; 97 hours since
  • Maximum gross weight: 2,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming 0-320-D2J (piston); 0 hours total
  • Operator: Florida Aviation Career Training, INC

The flight

  • Departed from: Unknown FL
  • Destination: Unknown FL
  • Flight plan: not recorded

Weather at the time

  • Light: daylight
  • Temperature: 0°F (-18°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Flight crew1

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

3 documents, released by the NTSB on September 7, 2012. 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.

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

2025-05-03ERA25LA194 · accident near Hastings, FL · substantial damage · minor injuries

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/ERA12CA466.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.