ERA11LA421 · Cessna 172S
Aero Safety Training Cessna 172S · Accident: landing area overshoot
From NO7 · Lincoln Park, NJ to NO7 · Lincoln Park, NJ
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA11LA421
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 172S
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N869BC
- Operator
- Aero Safety Training
- Onboard fatalities
- Unknown
- Route Possible conflict
- From NO7 · Lincoln Park, NJTo NO7 · Lincoln Park, NJ
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Landing area overshoot
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, the airplane experienced a total electrical failure shortly after takeoff, rendering the flaps inoperable. Witnesses observed the airplane land at a high rate of speed, two-thirds down the 2,942-foot runway. The airplane subsequently overran the runway and collided with a guardrail. The pilot reported that the airplane had poor braking performance and that it was not possible to stop on the remaining runway. Examination of the airplane’s wheel braking system revealed no preimpact mechanical malfunctions or failures that would have precluded normal operation. The airplane’s pilot operating handbook stated that the airplane is approved for a no-flap landing between 74 knots and 84 knots and requires a landing distance of 1,945 feet. Evidence indicates that the pilot landed too far down the runway to stop the airplane on the remaining runway. Examination of the airplane’s electrical system found an incorrect electrical contactor installed in the electrical master control unit, which resulted in overheating of the component and the loss of electrical power.
Probable cause
The pilot’s improper touchdown point, resulting in a runway overrun and collision with a guardrail.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11LA421
- Event ID
- 20110725X65622
- Case number
- ERA11LA421
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: a50e17de88042706a5167328a00d8961d2642307c352504fc1ab7e84ef00865e; retrieved 2026-09-15T16:30:29.177Z.