NYC97LA094 · Cessna 182P
Cessna 182P · Accident: overrun during landing
From Sky Park Airport (46N) to an unrecorded destination
Event
- NTSB case
- NYC97LA094
- 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
- 0
- 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 182P
- 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
- N7322S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sky Park Airport (46N)To not recorded
- 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 · landing roll
- 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 › Compensation for wind conditions, inadequate
- Pilot in command › Go-around, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane overran the runway and collided with trees during landing. The pilot reported that while landing he encountered strong, gusty winds. The pilot estimated the winds were from 270 to 290 degrees at a velocity of 15 knots. He stated that just prior to touchdown, the airplane encountered a gust '..from 290 that made the plane balloon.' According to the pilot, when the airplane settled to the runway the brakes locked, causing the plane to swerve onto the grass. He stated, 'I was able to steer it back to the runway but couldn't stop it before it went over the end of the runway and down the bank.' The airplane continued down the embankment and collided with trees. When asked how the accident could have been prevented, the pilot reported that 'the accident was a result of a failure to initiate a go-around procedure. The failure should have been avoided by having present in my mind pre-set parameters (maximum acceptable touchdown point) which should lead to an automatic decision to go around, avoiding the temptation to try to 'save' the landing simply because the wheels are on the ground. Training to this effect should be emphasized.'
Probable cause
The pilot's improper compensation for the wind conditions and his failure to initiate a go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC97LA094
- Event ID
- 20001208X08002
- Case number
- NYC97LA094
- 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. 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: 5e3718b8475ec1f19bca8b54364ec95eb8616e33ea890cacdba2363b3769ea5a; retrieved 2026-09-21T21:26:55.134Z.