# Accident 20130803016509A: Cessna 172S, Portsmouth, NH, August 3, 2013

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 3, 2013, 00:15 local time
- Place: Portsmouth, NH
- Damage: Substantial damage
- Phase of flight: Takeoff: Rotation
- Operating rules: General operating rules (Part 91)
- Location: 43.0778° N, 70.8231° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=43.0778&lon=-70.8231&mi=10
- Aircraft: N645PD, registered now (https://openairdocs.org/aircraft/N645PD) (OpenAirDocs)
- Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs)
- Registry engine: Lycoming I0360 SER A&C (registry code 41511, https://openairdocs.org/engine/lycoming-i0360-ser-a-c) (OpenAirDocs)
- Reported make and model: CESSNA 172S
- Reported engine: LYCOMING I0360 SER A&C
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- NTSB investigation: [NTSB ERA13CA350](https://openairdocs.org/ntsb/ERA13CA350) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20130803016509A

## Narrative

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

PILOT WHILE ON TAKE OFF ROLL HEARD A CONTINUOUS THUD OR BOUNCING SOUND.  PILOT DECIDED TO TAKE OFF. PILOT STATED THAT AFTER ROTATION, HE CLIMBED TO 10FT. AT THAT POINT HE RETURND TO GROUND UNDER FULL POWER.

NOSE GEAR PENETRATED FIREWALL CAUSING SIGNIFACANT DAMAGE TO NOSE GEAR AND FIREWALL.

## 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 ERA13CA350](https://openairdocs.org/ntsb/ERA13CA350), Aug 3, 2013: Cessna 172S (N645PD), Portsmouth, NH, substantial damage. Probable cause: The pilot’s inadequate preflight inspection resulting in his failure to remove the pin he used to lock the flight controls in place of the approved control lock.

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.