ANC94LA073 · Maule M-5
Maule M-5 · Accident: hard landing
From Homer, AK to an unrecorded destination
Event
- NTSB case
- ANC94LA073
- 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
Maule M-5
- Aircraft type
- Maule M-5
- 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
- N373X
- Operator
- Amberger, Mark E. · private individual
- Onboard fatalities
- Unknown
- Route
- From Homer, AKTo not recorded
- 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 · flare/touchdown
- 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
- Hard landing
- 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
- Landing gear, tire › Failure, total
- Pilot in command › Level off, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT DURING THE FIRST LANDING ATTEMPT THE AIRPLANE LANDED HARD AND BOUNCED, AND HE BALKED THE LANDING. DURING THE SECOND LANDING HE MADE A 3-POINT WHEEL TOUCHDOWN. THE AIRPLANE ROLLED UNEVENTFULLY FOR A SHORT DISTANCE, THEN VEERED UNCONTROLLABLY OFF THE STRIP INTO A DITCH. THE RIGHT WHEEL TIRE WAS FOUND TO HAVE A SLIT AND WAS DEFLATED.
Probable cause
THE PILOT'S IMPROPER LANDING TECHNIQUE WHICH RESULTED IN A HARD LANDING, TIRE FAILURE, AND EVENTUAL LOSS OF DIRECTIONAL CONTROL.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC94LA073
- Event ID
- 20001206X01423
- Case number
- ANC94LA073
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1994-07-01.
- API snapshot SHA-256: 2a3d4e578d0e223ba59c28c916a742c8524819fb1cfdf53ea248bf4352ef25f9; retrieved 2026-09-23T00:58:18.293Z.