FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Britt Airways Embraer EMB-120RT incident

9 Dec 1992 · Houston, TX, United States

Embraer EMB-120RT · Incident during initial climb

From George Bush Intercontinental Airport (IAH) to Esler Army Airfield / Esler Regional Airport (ESF)

Report a problem

Event

NTSB case
FTW93IA048
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-120RT

Aircraft type
Embraer EMB-120
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
N16729
Onboard fatalities
Unknown
Route
From George Bush Intercontinental Airport (IAH)To Esler Army Airfield / Esler Regional Airport (ESF), Alexandria, LA
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
Initial climb
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
Miscellaneous/other
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Company maintenance personnel › Maintenance, inspection, inadequate
  • Company maintenance personnel › Maintenance, installation, not performed

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

NTSB narrative

SHORTLY AFTER TAKEOFF THE FIRST OFFICER FELT A VIBRATION THROUGH THE AIRFRAME AND THE CONTROL COLUMN. THE CAPTAIN FELT THE SAME VIBRATION AND ELECTED TO EXECUTE A PRECAUTIONARY LANDING AT THE DEPARTURE AIRPORT. INVESTIGATION REVEALED THAT 14 SCREWS WERE MISSING FROM THE LEFT UPPER AILERON VANE AND THAT THE SCREWS HAD BEEN LEFT OUT AFTER THE VANE WAS PARTIALLY REMOVED DURING MAINTENANCE PRIOR TO THE FLIGHT. THE ASSIGNED MECHANIC DID NOT REPLACE THE SCREWS AND THE QUALITY CONTROL INSPECTOR FAILED TO SEE THAT THEY WERE MISSING DURING HIS INSPECTION.

Probable cause

THE ASSIGNED MECHANIC'S FAILURE TO REINSTALL THE ATTACHMENT SCREWS AND THE QUALITY INSPECTOR'S INADEQUATE INSPECTION OF THE COMPLETED WORK. A FACTOR WAS THE COMPLACENCY OF THE MAINTENANCE PERSONNEL.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW93IA048
Event ID
20001211X16157
Case number
FTW93IA048
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, damage. 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: c9ce0e9274c99f705a77f0dbd6c303ae977b4a53bf457312f7073dbb0efb5cb7; retrieved 2026-09-18T18:42:25.939Z.