Flight 711 · Beech BE-58
Beech BE-58 · Accident: loss of engine power during initial climb
From Fulton County Airport Brown Field (FTY) to Mobile Regional Airport (MOB)
Event
- NTSB case
- ATL99FA102
- 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
- 2 · 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
- Instrument Meteorological Cond
Beech BE-58
- Aircraft type
- Beechcraft BE-58
- 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
- N17915
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fulton County Airport Brown Field (FTY)To Mobile Regional Airport (MOB), Mobile, 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 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
- Loss of engine power
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Emergency procedure, not followed
- Reason for occurrence undetermined
Approximate · Estimated position: the centre of Atlanta, GA, the place the record names. Not the accident site.
NTSB narrative
Shortly after takeoff the pilot reported that he had an engine problem and requested to return to the airport. The controller cleared the flight to land on any runway. A witness reported hearing only one engine running. The pilot maneuvered west of the airport and subsequently collided with trees and burst into flames. Both propellers revealed low-pitch blade angle. No evidence of mechanical malfunction was found.
Probable cause
The loss of engine power for undetermined reasons, and the pilot's failure to follow emergency procedures that resulted in the uncontrolled collision with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL99FA102
- Event ID
- 20001212X18925
- Case number
- ATL99FA102
- 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: a6f1ecdc03e183ce28a4bb0b7477542ebe1c5d03d2ee26bce5fdf033e223cd4c; retrieved 2026-09-18T13:17:42.269Z.