ERA11FA468 · Mitchell David N LANCAIR IV P
Mitchell David N LANCAIR IV P and Yakovlev YAK-55M · Accident: midair collision while maneuvering
Event
- NTSB case
- ERA11FA468
- 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
- 1 · 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
Aircraft 1 · Mitchell David N LANCAIR IV P
- Aircraft type
- Mitchell David 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
- N71DM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From South Jersey Regional Airport (VAY), Mount Holly, NJTo Hammonton Municipal Airport (N81), Hammonton, 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
- Maneuvering
- 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Aircraft 2 · Yakovlev YAK-55M
- Aircraft type
- Yakovlev YAK-55
- 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
- N521BC
- Operator
- Barsukov Kirill
- Onboard fatalities
- Unknown
- Route
- From Hammonton Municipal Airport (N81), Hammonton, NJTo Hammonton Municipal Airport (N81), Hammonton, 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
- Maneuvering · aerobatics
- 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
- Midair collision
- 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
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The Lancair pilot told a witness that he was going to fly the high-performance airplane to a nearby airport to visit a friend. The pilot was aware that the nearby airport had occasional aerobatic activity near the runway, within an "aerobatic box." The box was active on the day of the accident, with a Notice to Airmen issued for aerobatic activity at 3,500 feet and below. The airplane approached the airport about 3,500 feet; however, the exact altitude could not be determined due to the fidelity of the radar/encoder data. As the airplane approached the airport at a high airspeed, likely about 190 knots, it collided with an aerobatic airplane that had just completed a hammerhead stall and was observed in a dive. The pilot's airplane cut through the aerobatic airplane's fuselage just aft of the cockpit, top to bottom, and lost about 4 feet of its left wing. The pilot's airplane then crashed into nearby woods, and the pilot of the aerobatic airplane parachuted into the same woods.
The aerobatic pilot and an observer stated that clearing turns were conducted prior to the aerobatic maneuver. However, the sun’s position and the airspeed of the oncoming airplane would have made it highly unlikely that the aerobatic pilot would have seen it. It is unknown what the inbound pilot's intentions were at the time of the accident. A relative of the inbound pilot, another pilot who had flown with him often, surmised that the pilot's approach to the airport at such a high altitude may have been an exploratory overflight, which is supported by the airplane's high airspeed at the time. Radar indicated that the pilot's airplane did not perform any standoff maneuvering prior to approaching the airport, and other pilots in the air at the time heard no advisory radio transmissions from him. During flight in visual meteorological conditions, the tenets of "see and avoid" apply. With the inbound pilot's knowledge of potential aerobatic activity at the airport, it is not known why he did not use advocated collision avoidance strategies.
Probable cause
The Lancair pilot's failure to see and avoid the aerobatic airplane. Contributing to the accident was the Lancair pilot's inadequate use of collision avoidance strategies while inbound to an area of known potential aerobatic activity.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11FA468
- Event ID
- 20110820X50228
- Case number
- ERA11FA468
- 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: d99cc95dbf987eea7a51a4cf34b4469561235c138e03da4ad53ca5b10242d24c; retrieved 2026-09-13T18:06:20.134Z.