# Accident 20160629010199A: Cessna 172R, Frederick, MD, June 29, 2016

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 29, 2016, 07:50 local time
- Place: Frederick, MD
- Airport: Frederick Municipal Airport
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: Pilot school (Part 141)
- Operator: LC1S
- Location: 39.4175° N, 77.3744° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=39.4175&lon=-77.3744&mi=10
- Aircraft: N2473G, registered now (https://openairdocs.org/aircraft/N2473G) (OpenAirDocs)
- Registry model: Cessna 172R (registry code 2072401, https://openairdocs.org/model/cessna-172r) (OpenAirDocs)
- Registry engine: Lycoming IO-360-L2A (registry code 41597, https://openairdocs.org/engine/lycoming-io-360-l2a) (OpenAirDocs)
- Reported make and model: CESSNA 172R
- Reported engine: LYCOMING IO-360-L2A
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 46 total, 46 in this make and model, 17 in the last 90 days
- NTSB investigation: [NTSB GAA16CA343](https://openairdocs.org/ntsb/GAA16CA343) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20160629010199A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

THE PILOT STATED THAT AT APPROXIMATELY 0845 ON JUNE 29, 2016 HE WAS CLEARED FOR LANDING ON RUNWAY 30 AT FREDERICK MUNICIPAL AIRPORT (KFDK) WHILE ON A SOLO TRAINING FLIGHT.  HE ALSO STATED THE APPROACH WAS STABLE AND WAS TRAINED FOR A FINAL APPROACH SPEED OF 70-75 KNOTS INDICATED AIRSPEED.  AFTER THE INITIAL TOUCH DOWN THE AIRCRAFT BOUNCED AND THE NEXT CONTACT WITH THE RUNWAY THE NOSE GEAR IMPACTED FIRST. THE AIRCRAFT WAS THEN TAXIED BACK TO THE RAMP AND WAS INSPECTED BY MECHANICS AT THE FLIGHT SCHOOL WHICH REVEALED A BENT FIREWALL WHICH WAS SUBSTANTIAL DAMAGE TO THE AIRFRAME.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB GAA16CA343](https://openairdocs.org/ntsb/GAA16CA343), Jun 29, 2016: Cessna 172 (N2473G), Frederick, MD, substantial damage. Probable cause: The student pilot's failure to maintain pitch control during the touch down resulting in a bounced landing, subsequent hard landing and substantial damage to the firewall.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.