ERA10CA030 · Cessna 182 R
Big Skylands Aviation Cessna 182 R · Accident: landing area overshoot
From Wilmington Airport (ILG) to Westchester County Airport (HPN)
Event
- NTSB case
- ERA10CA030
- 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 182 R
- Aircraft type
- Cessna 182
- 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
- N4731N
- Operator
- Big Skylands Aviation
- Onboard fatalities
- Unknown
- Route
- From Wilmington Airport (ILG), New Castle, DETo Westchester County Airport (HPN), White Plains, NY
- 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
- 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 › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that he approached the airport during night conditions and was told by air traffic control to expect runway 29. He glanced at the approach chart and noted the runway was more than 4,400-foot-long, but learned after the accident that it had a displaced threshold resulting in 3,164 feet being available for landing. He entered the downwind leg, then turned onto base leg when the controller requested he proceed direct to the numbers at the best forward speed. The pilot elected to land with no flaps and while on final approach, was advised by the controller to expedite through the intersection of runways 11/29 and 16/34. The airplane touched down past the runway intersection, which at the center has approximately 2,854 feet runway remaining to the departure end of runway 29. In a statement to the Federal Aviation Administration inspector-in-charge, the pilot-rated-passenger reported that the airplane's estimated speed to the runway was 110 knots. The pilot further stated that after touchdown, he was unable to stop the airplane. It traveled off the end of the runway, down an embankment, onto a service road and collapsed the nose landing gear. No preimpact malfunctions were reported by the pilot.
Probable cause
The pilot's failure to attain the proper touchdown point, resulting in a landing overrun. Contributing to the accident was the pilot’s excessive airspeed in an attempt to comply with air traffic control’s request to expedite his landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA030
- Event ID
- 20091026X20543
- Case number
- ERA10CA030
- 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, 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: c3df68ad5a6906251b48aa74bf3520fa3c6e7f67b5b5da10666806d1ecb9ffa2; retrieved 2026-09-15T13:26:24.009Z.