ERA14LA181 · Vans Aircraft Inc RV-12
Vans Aircraft Inc RV-12 and de Havilland DHC 1B 2-S3 · Accident: midair collision during landing
Event
- NTSB case
- ERA14LA181
- 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
Aircraft 1 · Vans Aircraft Inc RV-12
- Aircraft type
- Vans RV-12
- 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
- N409FM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cherry Ridge Airport (N30), Honesdale, PATo Bayport Aerodrome (23N), Bayport, NY
- Aircraft age
- About 4 years (built 2010)
- 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 · flare/touchdown
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Aircraft 2 · de Havilland DHC 1B 2-S3
- Aircraft type
- de Havilland DHC-1
- 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
- N12BH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bayport Aerodrome (23N), Bayport, NYTo Long Island MacArthur Airport (ISP), NEW YORK, NY
- Aircraft age
- About 58 years (built 1956)
- 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
- Initial climb
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 RV-12 was inbound for landing and had joined a 45-degree approach to the left base leg for the runway. The Chipmunk had taxied to the end of the runway to conduct an engine run-up. The pilot of the RV-12 said that he made a radio call on the common traffic advisory frequency (CTAF) while he was on the 45-degree base leg and during his turn to final. The Chipmunk pilot stated that he made a radio call on the CTAF stating his intention to depart. Both pilots said that they did not hear any traffic on the CTAF, nor did they see any traffic in the pattern or on the ground. The pilot of the RV-12 stated that the front half of the Chipmunk came into his view as the RV-12 was in its landing flare. Subsequently, the propeller of the RV-12 struck the rudder and vertical stabilizer of the Chipmunk, causing substantial damage and causing the RV-12 to lose thrust. A portion of the propeller blade tip from the RV-12 and a lead rudder balance weight from the Chipmunk were later discovered on the west half of the runway. The Chipmunk continued with the takeoff and landed shortly thereafter at a nearby airport. The RV-12 landed safely immediately after the collision.
Examination of the airport environment revealed that, depending on the angle and altitude of inbound aircraft and the position of aircraft on the ground, trees surrounding the approach end of the runway could block a pilot's view of arriving or departing aircraft.
Probable cause
The failure of both pilots to see and avoid each other, which resulted in a collision.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14LA181
- Event ID
- 20140406X50715
- Case number
- ERA14LA181
- 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: 10b847aeac610d918d1848cbcaf9e4007364276bc51a84be642250f1cf6b5013; retrieved 2026-09-13T18:23:04.987Z.