FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL02LA012 · Extra Flugzeugbau EA300/L

10 Nov 2001 · St. Augustine, FL, United States

Extra Flugzeugbau EA300/L and James D. Smith RV-3 · Accident: midair collision on approach

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's registration. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ATL02LA012
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 · Extra Flugzeugbau EA300/L

Aircraft type
Extra EA300
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
N2XA
Operator
Unknown
Onboard fatalities
Unknown
Route
From SGF · St. Augustine, FLTo 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
Approach · VFR pattern final
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
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
Minor

Aircraft 2 · James D. Smith RV-3

Aircraft type
James D Smith RV-3
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
N93HS
Operator
Raymond H. Smith · private individual
Onboard fatalities
Unknown
Route
From Haller Airpark (7FL4), Green Cove, FLTo 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 · flare/touchdown
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
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

  • Pilot in command › Visual lookout, not maintained
  • Pilot of other aircraft › Visual lookout, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

An Extra EA 300, N2XA and an RV-3, N92HS collided on the runway. The pilots of the Extra and the RV-3 attempted radio contact with UNICOM to obtain landing information. The pilots overhead landing directions from other pilots landing at the destination airport and entered the traffic pattern. Both pilot's stated they did not hear each other due to a lot of traffic on the UNICOM frequency and they continued to make position reports while in the traffic pattern. Both pilots reported following a Cessna airplane that was located ahead of them. The pilot of the RV-3 stated the Cessna pilot reported clear of the active runway and he reported his position on short final. As the wheels of his airplane touched the runway he felt an impact from above. He looked and observed the Extra on the runway. The pilot of the Extra stated he heard the Cessna pilot report clearing the active runway and continued making radio calls in the blind. He made a base turn to final with the left wing down for a crosswind correction. As he started to flare his airplane he felt a bump similar to a hard landing and observed what he thought was a wheel pan go past his canopy. He thought about making a go-around but elected to continue with the landing. He turned his airplane on the runway after landing and observed the RV-3 on the runway.

Probable cause

The pilot's failure to maintain a visual lookout and yield the right-of-way to a lower airplane while landing. This resulted in an inadvertent midair collision. Contributing to the accident was reported excessive radio communications on the UNICOM radio frequency resulting in both pilots not hearing the others transmission.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL02LA012
Event ID
20011116X02248
Case number
ATL02LA012
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: 63644e4d53cb13d510253d156fd706661b1faee7778b134a05535c5b9b530024; retrieved 2026-09-22T11:24:59.115Z.