FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA08LA174 · Schweizer Aircraft Corp G-164B

26 Aug 2008 · Clarksdale, MS, United States

Howard Flying Service Schweizer Aircraft Corp G-164B · Accident: system/component malfunction/failure (non-power) while taxiing

From Fletcher Field (CKM) to Fletcher Field (CKM)

Report a problem

Event

NTSB case
MIA08LA174
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

Schweizer Aircraft Corp G-164B

Aircraft type
Schweizer G-164
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
N3633S
Onboard fatalities
Unknown
Route
From Fletcher Field (CKM), Clarksdale, MSTo Fletcher Field (CKM)
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 137: Agricultural
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
Taxi · from runway
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
System/component malfunction/failure (non-power)
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

  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

While applying the left brake during taxi after landing, the pilot first heard a "loud pop from the left gear" and during further brake application, the left axle and wheel assembly separated. Two MS20008H22 bolts and one AN509-616-35 screw that secure the axle to the spring leg were fractured. The failure mode of the bolts was due to fatigue, and was typical of bolts that are insufficiently torqued. The mechanic who last inspected the airplane used his own checklist and did not torque check the bolts and screw, which is required by the manufacturer's Annual/100-Hour Airframe Inspection Checklist.

Probable cause

The mechanic’s failure to torque check the axle-to-spring gear attachment bolts per the manufacturer's Annual/100-Hour Airframe Inspection Checklist, resulting in fatigue failure of the bolts.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA08LA174
Event ID
20080918X01490
Case number
MIA08LA174
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. 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: a78b660298406c84fcb539644d5de5ce23bdb7b8e2d43ca53c42badfd29b9e0e; retrieved 2026-09-15T10:14:31.826Z.