ANC18LA030 · Champion 7GC
Champion 7GC · Accident: loss of control on ground during landing
From Merrill Field (MRI) to Merrill Field (MRI)
Event
- NTSB case
- ANC18LA030
- 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
Champion 7GC
- Aircraft type
- Champion 7
- 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
- N4844E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Merrill Field (MRI), Anchorage, AKTo Merrill Field (MRI), Anchorage, AK
- Aircraft age
- About 59 years (built 1959)
- 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
- 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 on ground
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was landing at the airport after a personal flight. After obtaining weather information for the destination airport, the pilot contacted the air traffic control (ATC) tower and requested to land on the runway that corresponded to the current wind condition. The pilot's intent was to land with a direct headwind. The controller responded that the requested runway was not available due to other airplanes landing and directed the pilot to land on another runway that would result in the airplane landing with a crosswind.
The pilot reported that the approach was stable. Upon touchdown, the airplane began to ground loop to the left, so she applied rudder and brake inputs as a corrective action, with no success. Subsequently, the right main landing gear separated, and the right wing impacted the runway; the airplane sustained substantial damage to the right wing and right aileron.
An examination of the main landing gear (right side) strut threaded sleeve and jam nut found that the oleo strut had fractured. Overstress fracture features were consistent with the sleeve fracturing from the end of the oleo strut assembly with the assembly loaded in tension.
No evidence of progressive or long-term cracking was observed on the fracture surface, which indicates that no cracks developed in the braze due to the low-tension loads during flight or due to attachment loads from assembly of the cap onto the strut cylinder assembly. Although the brazed joint between the sleeve and the oleo strut tube did not conform to the engineering drawing and the strength would have been substantially less than a properly brazed joint, there was no evidence to indicate that the joint would have separated if loaded as designed; the joint appeared to be strong enough to perform under normal operation given that there was no evidence of progressive fracture. Therefore, the strut likely fractured due to abnormal side loading of the wheel with little or no loads in the upward direction as the airplane tipped to the right during the landing sequence involving the ground loop to the left.
The pilot reported she should have "held firm" to her request to land with a headwind and not a direct crosswind or quartering tailwind. She further reported that in the "future I will be more firm in my requests as pilot in command for the runway that I feel comfortable with and will wait as necessary for tower permission to use my requested runway." It is likely that if the pilot had contacted the ATC tower again and waited to land to her original runway of choice, the landing would have had a direct headwind instead of a crosswind. The pilot's decision to land on a runway with a crosswind was likely due to self-induced pressure to land.
Probable cause
The pilot's failure to maintain directional control during landing with a crosswind, which resulted in a loss of control and failure of the main landing gear. Contributing to the accident was the pilot's self-induced pressure to land.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC18LA030
- Event ID
- 20180328X81341
- Case number
- ANC18LA030
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2018-03-26.
- API snapshot SHA-256: 851293818c8b3c80e98e25e819fe25bc2219fcadd23ce421a145f4b2736b5466; retrieved 2026-09-16T06:44:29.550Z.