Cessna 172S accident near Frederick, Maryland, June 17, 2012
On June 17, 2012 at about 9:30 pm local time, a Cessna 172S, registered N387AF, was substantially damaged in an accident during landing near Frederick, Maryland (Frederick airport). 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 pilot's inadequate landing flare, which resulted in a hard landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 17, 2012 · about 9:30 pm local time
- Place
- Frederick, Maryland · Frederick · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172S · all 172Ss on the register
- Registration
- N387AF · registry record · serial 172S10387
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
According to the pilot, his intent was to remain in the traffic pattern to practice takeoffs and landings on runway 23. During final approach, he had trouble maintaining alignment with the runway centerline. He applied power to correct the drift; however, the airplane impacted the runway left of centerline. The hard landing resulted in substantial damage to the firewall. The wind at the airport about the time of the accident was from 160 degrees at 9 knots. The pilot stated that there were no mechanical malfunctions or anomalies with the airplane.
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
- Hard landing during landing defining event
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 121 hours in all; 31 in this make and model; 8 in the last 90 days; 1 in the last 30 days; 15 as pilot in command
- Last flight review: April 3, 2012
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 2,159 hours
- Last inspection: 100-hour inspection, June 6, 2012; 20 hours since
- Maximum gross weight: 2,550 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming IO-360-L2A (piston); 0 hours total
- Operator: Kaufman Air INC
The flight
- Departed from: FDK Frederick MD at 9:25 pm
- Destination: FDK Frederick MD
- Flight plan: none
- Runway 23, 5,219 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 210° at 6 knots
- Visibility: 10 statute miles
- Sky: scat at 4,000 ft
- Temperature: 81°F (27°C), dew point 61°F (16°C)
- Altimeter: 30.15 inHg
- Observation at 9:15 pm from FDK
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
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 N387AF the same tail number, which may have belonged to a different aircraft at the time
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.