Aeromech Embraer EMB-110P1 incident
Embraer EMB-110P1 · Incident: airframe, component or system failure while taxiing
From Greensboro, NC to North Central West Virginia Airport (CKB)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ATL82IA034
- 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
- Incident
- 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
- Charter & commuter
- 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
Embraer EMB-110P1
- Aircraft type
- Embraer EMB-110
- 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
- N615KC
- Operator
- Aeromech
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Greensboro, NCTo North Central West Virginia Airport (CKB), Beckley, WV
- 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 135: Air Taxi & Commuter
- 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 · to runway
- 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Landing gear, normal retraction/extension assembly › Cross/stripped threaded
- Landing gear, normal retraction/extension assembly › Undertorqued
- Manufacturer › Condition(s)/step(s) insufficiently defined
Approximate · Estimated position: the centre of Clarksburg, WV, the place the record names. Not the accident site.
NTSB narrative
DURING TAXI OUT FROM GREENSBORO, NC, THE CAPTAIN NOTED THAT THE AIRCRAFT WAS PULLING TO THE RIGHT. THE PROBLEM ALLEVIATED ITSELF WHEN THE PILOT TAPPED THE RIGHT BRAKE. AFTER A NORMAL TAKEOFF, THE COPILOT NOTICED DURING GEAR RETRACTION THAT THE RIGHT MAIN WHEEL APPEARED TO BE CANTED OUT OF POSITION. AFTER THE GEAR RETRACTION CYCLE, THE GEAR IN-TRANSIT LIGHT REMAINED ILLUMINATED AND THE CREW DECIDED TO DIVERT TO THE OPERATORS BASE AT CLARKSBURG, WV. AFTER BURNING OFF FUEL, THE GEAR WAS LOWERED FOR LANDING AND IT WAS NOTED THAT THE RIGHT MAIN WHEEL WAS ROTATED 90 DEGREES TO ITS NORMAL POSITION. THE ENSUING PRECAUTIONARY LANDING WAS NORMAL WITH NO DAMAGE OR INJURY. INVESTIGATION REVEALED THAT THE RIGHT GEAR TORQUE LINK ASSEMBLY HAD BROKEN DUE TO STRIPPED THREADS ON SEVERAL OF THE ATTACHING BOLTS. THE STRIPPED THREADS ALLOWED A SIDE LOAD TO SHEAR THE LOCKING PLATE DURING NORMAL GROUND OPERATIONS. A REVIEW OF THE MAINTENANCE MANUAL REVEALED SPECIFIC TORQUE VALUES WERE NOT LISTED, THUS ALLOWING THE BOLTS TO BE UNDER TORQUED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL82IA034
- Event ID
- 20020917X01765
- Case number
- ATL82IA034
- 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. 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: 8fa760224724408f6faa1c89e28e2bd8a32b8fa9fcaba270bebc6727bff72518; retrieved 2026-09-18T21:13:20.646Z.