IAD05LA099 · Cessna 525
Cessna 525 · Accident: overrun during landing
From Delaware Coastal Airport (GED) to Old Bridge Airport (3N6)
Event
- NTSB case
- IAD05LA099
- 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 525
- Aircraft type
- Cessna 525
- 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
- N13FH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Delaware Coastal Airport (GED), Georgetown, DETo Old Bridge Airport (3N6), Old Bridge, 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
- First occurrenceThe 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
- Overrun
- 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
- Pilot in command › Performance data, not used
- Pilot in command › Preflight planning/preparation, improper
- Pilot in command › Proper touchdown point, not obtained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane departed with a full load of fuel, flew approximately 35 minutes, and upon touchdown, weighed approximately 9,500 pounds. According to data recovered from the Enhanced Ground Proximity Warning System, the approach became unstabilized 0.1 miles from the runway threshold, triggering an aural sink rate warning. The airplane touched down fast on the first 1/3 of the runway. The pilot realized the airplane would not stop in the remaining distance, so he aborted the landing; however, before becoming airborne, the airplane overran the runway, struck multiple objects, and was substantially damaged. According to performance information, at 9,500 pounds, on a wet runway, 3,550 feet was required, 306 feet greater than available.
Probable cause
The pilot's improper preflight planning, his failure to consult performance data, and his failure to obtain the proper touchdown point, which resulted in a runway overrun. Contributing factors to the accident were the excessive airspeed, overweight condition, and wet runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD05LA099
- Event ID
- 20050729X01119
- Case number
- IAD05LA099
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 7c698cd167a71f9d7c8900f221a09fe1ba75b6ea9115a0d2d4ba7c464640f976; retrieved 2026-09-21T18:57:22.783Z.