# Accident 20110410004919A: Cessna 172N, Millville, NJ, April 10, 2011

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 10, 2011, 11:35 local time
- Place: Millville, NJ
- Damage: Substantial damage
- Phase of flight: Takeoff: Rotation
- Operating rules: General operating rules (Part 91)
- Location: 39.3672° N, 75.0722° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=39.3672&lon=-75.0722&mi=10
- Aircraft: N6338F, registered now (https://openairdocs.org/aircraft/N6338F) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 3
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 82 total, 82 in this make and model, 20 in the last 90 days
- NTSB investigation: [NTSB ERA11CA236](https://openairdocs.org/ntsb/ERA11CA236) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20110410004919A

## Narrative

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

TWO PILOTS WHERE APPROACHING MIV WHERE THEY INTENDED TO SIMULATE AN INSTRUMENT APPROACH, THE ILS TO RWY 10, AND MAKE A FULL STOP. THE PILOT IN THE LEFT SEAT WAS TO MAKE THE LANDING, AND HAD ATTAINED CONCURRENCE FROM THE OTHER PILOT IN THE RIGHT SEAT TO USE NO FLAPS. ALTHOUGH HE THOUGHT THE AIRCRAFT WAS TOO FAST UPON REMOVING THE HOOD, HE CONTINUED THE APPROACH, LANDED LONG, AND PITCHED UP TO A NOSE HIGH  ATTITUDE. THE AIRCRAFT BOUNCED, RETURNED TO THE RUNWAY AND  CONTINUED FORWARD. EVIDENCE INDICATES BRAKES WHERE APPLIED AFTER CROSSING RWY14/32, WITH SKID MARKS APPROXIMATELY 100 FEET LONG FROM BOTH WHEELS STARTING JUST LEFT OF THE RUNWAY CENTER LINE AND CONTINUING TO APPROX 15 FEET PRIOR TO EDGE OF RUNWAY  JUST PAST TAXIWAY B. AT SOME POINT, THE PILOT IN THE RIGHT SEAT APPLIED FULL POWER PRIOR TO SKIDDING OFF THE RUNWAY. THE AIRCRAFT BECAME AIRBORNE FOR A GO AROUND, DEPARTING THE RUNWAY IN SAME DIRECTION AS THE SKID MARKS. THE  LEFT HORIZONTAL STABILIZER IMPACTED A  DISTANCE REMAINING SIGN LOCATED APPROXIMATELY 15 FEET FROM WHERE THE AIRCRAFT BECAME AIRBORNE, JUST TO THE LEFT OF  THE RUNWAY AND TURN OFF FOR TAXIWAY  B. THE SIGN WAS DESTROYED, CAUSING SUBSTANTIAL DAMAGE TO THE OUTBOARD LEFT HORIZONTAL STABILIZER AND SHEARING OFF THE LEFT ELEVATOR.THE RIGHT SEAT PILOT CONTINUED WITH THE GO AROUND AND ENTERED LEFT TRAFFIC FOR RWY 14. HE LANDED UNDER POWER AND TAXIED TO THE RAMP WITHOUT FURTHER INCIDENT.

## 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 ERA11CA236](https://openairdocs.org/ntsb/ERA11CA236), Apr 10, 2011: Cessna 172N (N6338F), Millville, NJ, substantial damage. Probable cause: The pilot’s improper recovery from a bounced landing which resulted in a loss of aircraft control during the go-around.

## Other reports on N6338F (2)

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

- [Accident 20020704018149A](https://openairdocs.org/incident/20020704018149A), Jul 4, 2002: Cessna 172N (N6338F), Fulton, NY, No damage. (-23) On July 4, 2002 at 1045 eastern daylight time, Cessna 172, N6338F, was substantially damaged while landing on runway 24 at the Oswego County Airport…
- [Accident 19950814049199A](https://openairdocs.org/incident/19950814049199A), Aug 14, 1995: Cessna 172 (N6338F), Fulton, NY, Substantial damage. (-16) Aircraft damage was caused by pilot executing a hard landing during an instructional period. [privacy data omitted]

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.