GAA16CA300 · Costruzioni Aeronautiche Tecna P2002 SIERRA JF
Costruzioni Aeronautiche Tecna P2002 SIERRA JF · Accident: loss of control in flight during landing
From Saginaw County H.W. Browne Airport (HYX) to Marshall County Airport (MPG)
Event
- NTSB case
- GAA16CA300
- 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
Costruzioni Aeronautiche Tecna P2002 SIERRA JF
- Aircraft type
- Tecnam P2002
- 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
- N323TC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Saginaw County H.W. Browne Airport (HYX), Saginaw, MITo Marshall County Airport (MPG), Moundsville, WV
- Aircraft age
- About 8 years (built 2008)
- 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 · flare/touchdown
- 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
- Loss of control in flight
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that as the airplane entered the landing flare, a crosswind gust "picked up the right wing." He further reported that he applied full power to go-around, and the airplane drifted to the left. Subsequently, the airplane struck trees next to the runway, which resulted in substantial damage to the fuselage, firewall, and both wings.
The pilot did not report any mechanical malfunctions or failures with the airplane that would have precluded normal operation.
The nearest automated weather observing station, which was 18 nautical miles north of the accident airport, about the time of the accident, reported the wind at 320 degrees true at 10 knots gusting to 16 knots. The pilot reported that he landed on a runway with a 240 degrees magnetic heading.
Probable cause
The pilot's failure to maintain directional control during the go-around in gusty crosswind conditions, which resulted in a collision with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA300
- Event ID
- 20160613X95657
- Case number
- GAA16CA300
- 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, 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: 23a3febda4aa0380aad4f59f78874ef9ea05568107a9392f18ba097ba8436901; retrieved 2026-09-16T03:30:34.571Z.