ATL04IA067 · Sabreliner Corp. NA-265-60
Sabreliner Corp. NA-265-60 · Incident: airframe, component or system failure during landing
From Savannah Hilton Head International Airport (SAV) to Birmingham-Shuttlesworth International Airport (BHM)
Event
- NTSB case
- ATL04IA067
- 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
- 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
Sabreliner Corp. NA-265-60
- Aircraft type
- Sabreliner NA-265
- 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
- N124DC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Savannah Hilton Head International Airport (SAV), Savannah, GATo Birmingham-Shuttlesworth International Airport (BHM), Birmingham, AL
- 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
- 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
- None
Cause areas
- Landing gear, wheel
- Lubricant, grease › Lack of
- Miscellaneous, bolt/nut/fastener/clamp/spring › Overtemperature
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
After landing at the Birmingham International Airport, Alabama it was discovered that the right main wheel was missing off of the landing gear assembly. Further examination of the right main wheel revealed that the bearings had failed and the wheel passed over the axle assembly. The Birmingham Flight Standards District Office of the Federal Aviation Administration requested assistance with the metallurgical examination of the right main landing gear bearing assembly. Examination of the outer bearing revealed temperature exposure and severe rubbing. The examination of the bearing assembly also revealed that no grease or lubricant was present on the fragmented pieces of the bearing.
Probable cause
The lack of lubrication of the right main wheel bearing which resulted in the overheating.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL04IA067
- Event ID
- 20040127X00114
- Case number
- ATL04IA067
- 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, coordinates, 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: 2fadbaddf9de0332ac9b027f133bd4f52d4ced461552e574668270b0f4d968aa; retrieved 2026-09-22T08:03:21.932Z.