IAD97LA066 · Globe GC-1-A
Globe GC-1-A · Accident: loss of control on ground/water during landing
From 19I · Lebanon, OH to Clinton County Airport (I66)
Event
- NTSB case
- IAD97LA066
- 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
- 0
- 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
Globe GC-1-A
- Aircraft type
- Globe GC-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
- N80523
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 19I · Lebanon, OHTo Clinton County Airport (I66), 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
- Landing
- 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
- Loss of control on ground/water
- 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 › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was practicing crosswind landings on runway 20. He performed a three point landing, and during the roll-out, the airplane drifted off the right side of the runway into the wind. He applied full power to regain directional control, and raised the flaps. The airplane became airborne in ground effect, flew over the runway, and collided with trees off the left side. A witness said he observed the airplane land with a tailwind. When the airplane began to drift off the right side of the runway, the pilot applied full power, and the left wing tip almost touched the runway twice. At an airport 6 miles south, the winds were reported from 310 degrees at 10 knots, with gusts to 18 knots. The pilot reported over 586 hours of total flight experience, which included 3 hours in make and model. The pilot reported there was no mechanical malfunction with the airplane, and the accident could have been prevented with 'better pilot preparation.'
Probable cause
failure of the pilot to maintain directional control of the airplane during the landing, which resulted in a collision with trees. Related factors were: the crosswind, and lack of experience in the make and model of airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD97LA066
- Event ID
- 20001208X07729
- Case number
- IAD97LA066
- 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: ce5f4a0baf10c1c8f0ea8595382c0cde6566c738ae64c3822308c8ebcf166b7b; retrieved 2026-09-22T19:56:01.775Z.