ATL83LA283 · Cessna 310
Cessna 310 · Accident: airframe, component or system failure on approach
From Ocean City, MD to an unrecorded destination
Event
- NTSB case
- ATL83LA283
- 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
- Unknown
Cessna 310
- Aircraft type
- Cessna 310
- 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
- N3066L
- Operator
- Daniel Haloszka
- Onboard fatalities
- Unknown
- Route
- From Ocean City, MDTo 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
- Approach
- 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
- Substantial
Cause areas
- Landing gear, gear locking mechanism › Unlocked
- Other maintenance personnel › Maintenance, inspection, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING THE APCH, THE PLT WAS UNABLE TO GET A SAFE DOWN INDICATION FOR THE RIGHT MAIN GEAR. HE CHANGED THE LIGHT BULB & STILL DID NOT GET A SAFE INDICATION. A TOWER FLYBY WAS MADE, BUT THE TOWER OPERATOR WAS UNABLE TO CONFIRM IF THE RIGHT GEAR WAS LOCKED. TO TEST THE GEAR, THE PLT MADE A LANDING APPROACH TO THE RWY & ALLOWED THE ACFT TO TOUCHDOWN MOMENTARILY. HE RECALLED THAT THE RIGHT SIDE SETTLED LOWER THAN THE LEFT SIDE, SO HE BURNED OFF EXCESS FUEL, AND DECIDED TO LAND WITH THE OTHER TWO GEAR DOWN & LOCKED. DURING THE LANDING, THE PLT WAS UNABLE TO KEEP THE ACFT ON THE RWY. IT VEERED OFF THE RIGHT SIDE OF THE RWY, & AFTER TRAVELING APRX 2000 FT, IT CAME TO REST WITH THE RIGHT MAIN GEAR COLLAPSED. AN INVESTIGAITON INDICATED THE RIGHT PUSH-PULL TUBE ASSY WAS BENT FROM OVERLOAD. REPORTEDLY, NO RECORD WAS FOUND IN THE MAINTENANCE LOG TO SHOW THAT THE REQUIRED 200 HR GEAR RIG CHECK WAS ACCOMPLISHED.THE ACFT HAD 1999 HRS TOTAL FLT TIME. THE SVC MANUAL STATED THE GEAR MAY NOT FULLY EXTEND IF IT IS OUT OF RIG.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL83LA283
- Event ID
- 20001214X43623
- Case number
- ATL83LA283
- 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: 84bc8beac2d3fa49749042aaa117c396b7e813fb4a6c19b6412c1750f1f71a6a; retrieved 2026-09-23T21:44:20.469Z.