ERA09CA219 · Parks Jerry R LANCAIR 235/320
Parks Jerry R LANCAIR 235/320 · Accident: loss of control in flight during landing
From Peter Prince Field (2R4) to Peter Prince Field (2R4)
Event
- NTSB case
- ERA09CA219
- 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
Parks Jerry R LANCAIR 235/320
- Aircraft type
- Parks Jerry LANCAIR
- 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
- N320J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Peter Prince Field (2R4), Milton, FLTo Peter Prince Field (2R4), Milton, FL
- 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
- Loss of control in flight
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Following a local flight, the pilot attempted to land on runway 18. The pilot reported that, approximately 10 feet above the runway, a gust of wind caused the right wing to rise "about 30 degrees from level." Even though the pilot added power, "and put the ailerons and rudder full right," the airplane "did not respond" and veered to the left. The airplane impacted the ground to the left of the runway, substantially damaging the wings, tail, fuselage, and engine. The pilot sustained minor injury. The airport had an automated surface observing system (ASOS); however, it did not have the ability to record weather observations. The pilot stated that the ASOS reported "windshear" before his departure and that the winds were from 210 degrees at 10 knots with gusts to 25 knots. The reported weather at nearby airports included gusty winds from the southwest, between 9 and 24 knots, before and after the accident. One of these airports reported a peak wind of 28 knots from 240 degrees approximately 4 minutes after the accident. The pilot reported that the pilot's operating handbook for the airplane stated that the maximum demonstrated crosswind was "20 knots."
Probable cause
The pilot's failure to maintain aircraft control during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09CA219
- Event ID
- 20090329X02720
- Case number
- ERA09CA219
- 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: 931a0ec462382e119d6688d79b496710fa690fc0bf6c4d23ac55490bf40c9472; retrieved 2026-09-15T10:52:54.260Z.