CEN10LA487 · Shpakow Thomas SA 750
Shpakow Thomas SA 750 · Accident: collision during takeoff/landing on approach
From Centennial Airport (KAPA) to Brighton Van-Aire Estates Airport (CO12)
Event
- NTSB case
- CEN10LA487
- 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
Shpakow Thomas SA 750
- Aircraft type
- Shpakow Thomas SA-750
- 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
- N28KT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Centennial Airport (KAPA), Centennial, COTo Brighton Van-Aire Estates Airport (CO12), Brighton, CO
- 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 go-around
- 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
- Collision during takeoff/landing
- 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 › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During a local fly-in event, a radio controlled airplane collided with a bi-plane while the bi-plane was performing a go-around. The radio controlled airplane was performing a hover maneuver just prior to the collision and initiated an escape maneuver which placed the radio controlled airplane right into the flight path of the bi-plane. The bi-plane sustained substantial damage, but was able to land without further incident. The radio controlled airplane was destroyed. Prior to the event, the event coordinator briefed the participants that they were to operate their radio controlled airplanes to the east of the runway, and not directly in the runway environment. While the event coordinator was monitoring the radio for traffic, it was not clearly communicated who, if anyone, was providing spotter duties for the radio controlled airplane operator prior to the collision.
Probable cause
The radio-controlled airplane operator’s decision to maneuver his airplane outside of the designated operating area, resulting in a collision with a bi-plane. Contributing to the accident was the lack of a formally designated spotter.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10LA487
- Event ID
- 20100819X52836
- Case number
- CEN10LA487
- 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: 533e61437f2213e496a4d0e1cea38fe043aebc1e255e8bae5d78d272c8b7d5a0; retrieved 2026-09-15T14:53:13.106Z.