ATL89LA133 · Beech A36
Beech A36 · Accident: airframe, component or system failure en route
From Gainesville Regional Airport (GNV) to Hartsfield Jackson Atlanta International Airport (ATL)
Event
- NTSB case
- ATL89LA133
- 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
- Visual Meteorological Cond
Beech A36
- Aircraft type
- Beechcraft 36
- 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
- N6613A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Gainesville Regional Airport (GNV), Gainesville, FLTo Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GA
- 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
- En route · cruise
- 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
- Pilot in command › Emergency procedure, not followed
- Pilot in command › Procedures/directives, not followed
- Pilot in command › Remedial action, delayed
- Pilot in command › Self-induced pressure
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
PIC NOTED AMMETER INDICATED DISCHARGE DURING FLT. HE DECLINED TO DIVERT & LAND TO ASSESS MALFUNCTION UNTIL TOTAL LOSS OF ELECTRICAL POWER. LDG GEAR EXTENDED NORMALLY AT BEGINNING OF DESCENT FROM 6000 FT. USING HAND HELD RADIO PIC ASKED TWR CONTROLLER TO EXAMINE LDG GEAR WHO RPTED IT WAS DOWN. MANUAL EXTENSION WAS NOT DONE IAW FLIGHT MANUAL EMER PROCEDURES. AFTER FLY BY OIL PRESS GAGE WENT TO ZERO. PIC DECIDED TO LAND IMMEDIATELY, NOSE & RT MAIN GEAR COLLAPSED ON TOUCHDOWN.
Probable cause
THE PILOT DELAYED REMEDIAL ACTION WHEN THE IMMINENT LOSS OF ELECTRICAL POWER WAS OBSERVED. ADDITIONALLY, THE PILOT'S FAILURE TO EXECUTE THE APPROPRIATE EMERGENCY PROCEDURE AND MANUALLY LOWER THE LANDING GEAR, RESULTED IN ITS COLLAPSE UPON LANDING. CONTRIBUTING TO THE ACCIDENT WAS THE PILOT'S LACK OF KNOWLEDGE REGARDING THE POWER SOURCE FOR THE AIRPLANE INSTRUMENTATION. WHEN CONFRONTED WITH THE ZERO OIL PRESSURE INDICATION THE PILOT'S SELF INDUCED PRESSURE PRECIPITATED AN UNNECESSARY HURRIED LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL89LA133
- Event ID
- 20001213X28035
- Case number
- ATL89LA133
- 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: 033ed08a048aac31d6fd1ce2b1ecbb29c8fd7d9b7d04d2ba7ead05b95aebcc72; retrieved 2026-09-23T07:41:08.004Z.