CHI06FA010 · Plavcan Lancair 235
Plavcan Lancair 235 and American Winds Flight Academy Cessna 172L · Accident: midair collision en route
Event
- NTSB case
- CHI06FA010
- 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
- 4 · 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 · Plavcan Lancair 235
- Aircraft type
- Plavcan LANCAIR 235
- 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
- N235U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Carroll County-Tolson Airport (TSO), Carrollton, OHTo 29G · Ravenna, OH
- 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
- En route · cruise
- 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
- Destroyed
Aircraft 2 · Cessna 172L
- Aircraft type
- Cessna 172
- 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
- N7768G
- Operator
- American Winds Flight Academy
- Onboard fatalities
- Unknown
- Route
- From Akron Fulton International Airport (AKR), Akron, OHTo 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
- Maneuvering
- 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
- Destroyed
Cause areas
- Pilot in command › Visual lookout, inadequate
- Pilot of other aircraft › Visual lookout, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
A Lancair 235 airplane and a Cessna 172L airplane were destroyed when they collided in midair during day visual meteorological conditions. The Lancair departed on a personal flight from an airport approximately 38 miles south of the accident site, for a destination airport about 8 miles north-northwest of the accident site. Radar track data depicted the Lancair's flight path as north-northeast, on a direct path to the destination airport, at an altitude between 2,200 to 2,500 feet msl. The Cessna departed an airport about 15 miles west-southwest of the accident site, and flew eastbound with a flight instructor and dual student on an instrument training flight. Radar data indicated that the flight had numerous heading and altitude changes, consistent with the training mission. According to radar track data, during the final minute prior to the collision, the Lancair was on true course of about 356 degrees, with a ground speed of approximately 145 knots. The Cessna was on a true course of about 295 degrees, with a ground speed of approximately 100 knots, and an altitude of 2,300 feet. The relative angle as extrapolated from radar data, indicates that the Cessna would have been positioned about 45 degrees to the right of the Lancair's nose, and the Lancair would have been approximately 80 degrees to the left of the Cessna's nose. A witness to the accident stated that both airplanes appeared to be in straight and level flight prior to impact. Neither airplane was under air traffic control. Federal Air Regulations state that vigilance shall be maintained by each person operating an aircraft so as to see and avoid other aircraft. Postaccident inspection disclosed no evidence of any preimpact mechanical anomalies with either airplane.
Probable cause
The failure of both pilots to maintain an adequate visual lookout during cruise flight, which resulted in their failure to see and avoid each other and a midair collision.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI06FA010
- Event ID
- 20051019X01689
- Case number
- CHI06FA010
- 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, 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: 7648ea2dd0c357f2bf24e27f6633830188c729dfee3873baa4fc4a0f81199511; retrieved 2026-09-20T17:49:28.120Z.