CHI02LA226 · Giroux Air Cam
Giroux Air Cam · Accident: in flight collision with object during landing
From Topeka Regional Airport (FOE) to Ozawkie, KS
Event
- NTSB case
- CHI02LA226
- 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
Giroux Air Cam
- Aircraft type
- Giroux AIR CAM
- 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
- N1029G
- Operator
- Guy Giroux
- Onboard fatalities
- Unknown
- Route
- From Topeka Regional Airport (FOE), Topeka, KSTo Ozawkie, KS
- 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 · aborted
- 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
- In flight collision with object
- 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
- Pilot in command › Aborted landing, delayed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The amateur built airplane collided with trees during the climb phase of an aborted landing. The pilot reported that while on short final the airplane seemed to be traveling faster than normal although the airspeed indicator was indicating a normal approach speed of about 45 mph. He stated the airplane floated during the landing. He reported that he applied the brakes when the main gear touched down, but the airplane still seemed to be going too fast. He stated that he decided to go around when he reached a point approximately two-thirds the way down the 650 foot long landing area. The pilot reported he added full power, but was unable to gain sufficient altitude to clear trees at the end of the landing area. The airplane contacted the trees at an estimated altitude of about 20 feet. The pilot reported the landing area was a combination of a gravel driveway and grass area. He stated the normal landing distance for the airplane is about 250 feet. The normal takeoff distance with two adults and at gross weight is about 160 feet. The landing was being made to the west and the pilot reported the local winds were from the west southwest at 5 to 8 knots.
Probable cause
The pilot's delay in aborting the landing. A contributing factor was the excessive airspeed.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI02LA226
- Event ID
- 20020802X01289
- Case number
- CHI02LA226
- 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: 882a373075c2eb909261f6ff5c697de4ce6919dd9f21b3d01a26a8f2a7bd00ee; retrieved 2026-09-22T10:37:30.669Z.