CHI07CA130 · Boeing E75N1
Boeing E75N1 · Accident: loss of control on ground/water during landing
From Youngstown Elser Metro Airport (4G4) to Fostoria Metropolitan Airport (FZI)
Event
- NTSB case
- CHI07CA130
- 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
Boeing E75N1
- Aircraft type
- Boeing E75
- 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
- N3840K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Youngstown Elser Metro Airport (4G4), Youngstown, OHTo Fostoria Metropolitan Airport (FZI), Fostoria, 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
- 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 › Compensation for wind conditions, inadequate
- Pilot in command › Directional control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The tail-wheel airplane was substantially damaged during landing when it departed runway 27 (4,198 feet by 100 feet, asphalt) and nosed over. The pilot noted that the intended destination was a planned fuel stop en route to his final destination. He stated that upon "entering the traffic pattern, it was apparent that the winds were stronger than forecast from the south. Upon landing, a gust of wind struck the plane." The airplane subsequently departed the runway pavement and nosed over. Surface winds in the vicinity were reported to be from 210 degrees at 19 knots, gusting to 30 knots. The pilot noted that there were no malfunctions associated with the airplane prior to the accident.
Probable cause
The pilot's inadequate compensation for wind conditions and his subsequent failure to maintain directional control during landing. The crosswind and wind gusts were contributing factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI07CA130
- Event ID
- 20070518X00586
- Case number
- CHI07CA130
- 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: 07a84cdbbf517d9090c2ec1571136bb1add9d5e60b702f028929043cea46b1d4; retrieved 2026-09-22T03:56:01.701Z.