# NTSB NYC06CA077: Cessna 172S, N680SP, Atlantic City, NJ, March 6, 2006

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: March 6, 2006, 18:00 local (23:00 UTC)
- Place: Atlantic City, NJ
- Coordinates: 39.356109, -74.453613
- Nearby events: https://openairdocs.org/map.md?lat=39.3561&lon=-74.4536&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report May 30, 2006
- Report: Approved by Office Director
- NTSB case key (mKey): 63328
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC06CA077
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/63328/pdf
- Page: https://openairdocs.org/ntsb/NYC06CA077

## Probable cause

The pilot's failure to obtain a proper touchdown point, which resulted in an overrun of the runway.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Overrun, landing
  - proper touchdown point - not attained, pilot in command (cause)
- On ground/water encounter with terrain/water, landing - roll
  - terrain condition - ground

## Analysis

As the pilot approached the runway, the visual approach slope indicator showed that the airplane was on a proper glidepath.  During the landing, the airplane encountered ground effect and floated down the runway.  The pilot contemplated aborting the landing, but subsequently elected to continue.  After touchdown he applied "full brakes," but the airplane overran the end of the runway, and was substantially damaged.  The pilot reported no mechanical malfunctions associated with the airplane.

## Factual narrative

As the pilot approached the runway, the visual approach slope indicator showed that the airplane was on a proper glidepath.  During the landing, the airplane encountered ground effect and floated down the runway.  The pilot contemplated aborting the landing, but subsequently elected to continue.  After touchdown he applied "full brakes," but the airplane overran the end of the runway, and was substantially damaged.  The pilot reported no mechanical malfunctions associated with the airplane.

## Aircraft

- Registration: [N680SP](https://openairdocs.org/deregistered/N680SP-2013-05-22), registration cancelled 2013-05-22, S/N 172S8091, built 1999 (OpenAirDocs)
- Reported make and model: Cessna 172S
- Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs)
- Registry engine: [Lycoming I0360 series](https://openairdocs.org/engine/lycoming-i0360-series) (registry code 41515, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 172S8091
- Engines: Lycoming IO-360 reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Ken Nierenberg, doing business as Flight School
- Registered owner: Venture Flight Inc.
- Airworthiness certificate: Standard, Normal
- Departed: 39N, Princeton, NJ
- Destination: AIY, ATLANTIC CITY, NJ
- Flight plan: VFR
- Airport: KAIY, Atlantic City/Bader Field, runway 11

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 20; injuries: none; private; airplane ratings: single-engine land; medical: class 2; flight hours: 160 total, 92 in this make and model, 75 as pilot in command, 30 in the last 90 days, 14 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 90° at 6 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 36 °F, dew point 21 °F
- Altimeter: 29.98 inHg
- Observed at: KACY

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20060306012079A](https://openairdocs.org/incident/20060306012079A), Mar 6, 2006: Cessna 172S, Atlantic City, NJ, Substantial damage. (-23) Pilot touched down more than half way down runway 11 and was unable to stop the aircraft on the runway.

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.

---
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.