ATL01FA027 · Beech F90-42
Amprite Aviation Beech F90-42 · Accident: loss of engine power during initial climb
From Nashville International Airport (BNA) to VES · Waukesha, WI
Event
- NTSB case
- ATL01FA027
- 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
- 4 · 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
Beech F90-42
- Aircraft type
- Beechcraft 90
- 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
- N17AE
- Operator
- Amprite Aviation
- Onboard fatalities
- Unknown
- Route
- From Nashville International Airport (BNA), Nashville, TNTo VES · Waukesha, WI
- 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
- 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
- Pilot in command › Propeller feathering, not performed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Shortly after takeoff at less than 200 feet above ground level the pilot reported an engine failure, and requested to return to the airport. The controller saw the airplane in a right turn, descending, and observed the airplane level its wings just prior to impact with the tips of trees. The airplane collided with terrain approximately 2,000 feet east of the approach end of runway 20L. A post crash fire ensued and consumed a majority of the airplane. Examination of both engines displayed contact signatures to their internal components characteristic of the engines being powered, with the propellers out of feather at the time of impact, and a low power range. Examination of the propellers found the left propeller blades showed more damage then the blades from the right propeller. Both propellers were rotating with considerable rotational energy. However, examination showed that the left propeller had more power then the right.
Probable cause
The pilot's failure to follow loss of engine power emergency procedures by not feathering the propeller following the loss of engine power for undetermined reasons, resulting in a descent and collision with trees and the ground.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL01FA027
- Event ID
- 20010206X00396
- Case number
- ATL01FA027
- 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. 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: d3128fb2adcea699905d33393ed41c916576ef414a13c1130d25a68f896a596c; retrieved 2026-09-20T20:40:57.642Z.