# Accident 20130822016869A: Cessna 172S, Manassas, VA, August 22, 2013

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 22, 2013, 09:28 local time
- Place: Manassas, VA
- Airport: Manassas Regional/Harry P. Davis F
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Operator: IBIS
- Location: 38.8072° N, 77.5089° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=38.8072&lon=-77.5089&mi=10
- Aircraft: N740SP, registered now (https://openairdocs.org/aircraft/N740SP) (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: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 33 total, 33 in this make and model
- NTSB investigation: [NTSB ERA13CA371](https://openairdocs.org/ntsb/ERA13CA371) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20130822016869A

## Narrative

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

N740SP RECEIVED SUBSTANTIAL DAMAGE DURING AN APPROACH AND ATTEMPTED LANDING AT MANASSAS AIRPORT (HEF) ON THURSDAY AUGUST 22, 2013 AT APPROXIMATELY 0928 LOCAL TIME.  THE AIRCRAFT LANDED IN A 3-POINT LANDING WITH WHAT WAS DESCRIBED AS "EXCESSIVE SPEED" BY A WITNESS.  THE AIRCRAFT LANDED IN THE FIRST THIRD OF THE RUNWAY BUT BEGAN A PORPOISING MOTION THAT BECAME UNCONTROLLABLE FOR THE STUDENT PILOT.  INSTEAD OF ATTEMPTING TO "GO-AROUND," THE PILOT SAID THAT HE BECAME FIXATED ON THE DETERIORATING SITUATION AND INSTEAD TRIED TO FIX THE OSCILLATIONS.  ON APPROXIMATELY THE THIRD OSCILLATION, THE NOSE GEAR HIT WITH ENOUGH FORCE TO CAUSE THE NOSE GEAR TO BE TORN FROM THE STRUT.  THE AIRCRAFT CONTINUED DOWN THE RUNWAY SCRAPING THE REMAINS OF THE NOSE GEAR STRUT AND VEERING OF TO THE RIGHT HAND SIDE OF THE RUNWAY (16R).  FOR THE FIRST 54 FEET OF RUNWAY GOUGING, THERE WERE ASSOCIATED SIGNS OF REPEATED PROP STRIKES.  THERE WAS ANOTHER 243 FEET OF GOUGES IN THE RUNWAY WITHOUT EVIDENCE OF PROP STRIKE UNTIL THE AIRCRAFT REACHED THE GRASS.  AT THE POINT WHERE THE AIRCRAFT ENTERED THE GRASS, THE REMAINS OF THE NOSE STRUT DUG INTO THE TURF CAUSING A FORWARD MOVEMENT, WHICH IN TURN CAUSED THE AIRCRAFT SPINNER TO DIG FURTHER INTO THE TURF.  THE REMAINING INERTIA OF THE AIRCRAFT FLIPPED THE AIRCRAFT OVER IN TO AN INVERTED POSITION.  THE PILOT WAS ABLE TO FREE HIMSELF WITHOUT AID.  FLIGHT SCHOOL PERSONNEL WHO WITNESSED THE ACCIDENT HELPED SECURE THE ENGINE.  EMERGENCY PERSONNEL WERE ON SCENE WHEN THE FAA ARRIVED.

## 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 ERA13CA371](https://openairdocs.org/ntsb/ERA13CA371), Aug 22, 2013: Cessna 172S (N740SP), Manassas, VA, substantial damage. Probable cause: The student pilot’s improper recovery from a bounced landing.

## Other reports on N740SP (2)

Matched to the same aircraft by N-number and date.

- [Accident 20250309008809A](https://openairdocs.org/incident/20250309008809A), Mar 9, 2025: Cessna 172S (N740SP), Brooksville, FL, Substantial damage. PIC departed runway 21 in Brooksville, FL. PIC was making a left traffic pattern. PIC did a normal landing procedure, full flaps, pitching for 75 KTS. PIC…
- [Accident 20150610008689A](https://openairdocs.org/incident/20150610008689A), Jun 10, 2015: Cessna 172S (N740SP), Galesburg, IL, Substantial damage. The jet air aircraft came in June 10, 2015 from burlington, IA for a 50 hr. Inspection at the Galesburg airport. Upon inspecting the engine, it was noted that…

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.