CEN18FA050 · Smith AEROSTAR 601
Smith AEROSTAR 601 · Accident: loss of control in flight on approach
From Miami Executive Airport (TMB) to Miami Executive Airport (TMB)
Event
- NTSB case
- CEN18FA050
- 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
- 1 · 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
Smith AEROSTAR 601
- Aircraft type
- Smith AEROSTAR 601
- 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
- N7529S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Miami Executive Airport (TMB), Miami, FLTo Miami Executive Airport (TMB), Miami, FL
- Aircraft age
- About 43 years (built 1974)
- 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
- Defining eventThe 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 control in flight
- 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
- Not determined › Not determined
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Before departing on the flight, the private pilot, who did not hold a current medical certificate, fueled the multiengine airplane and was seen shortly thereafter attempting to repair a fuel leak of unknown origin. The pilot did not hold a mechanic certificate and review of the maintenance logbooks revealed that the most recent annual inspection was completed 2 years before the accident. After performing undetermined maintenance to the airplane, the pilot reported to a witness that he had fixed the fuel leak. The pilot then taxied to the runway for takeoff. Witnesses reported that a large fuel stain was present on the ramp where the airplane had been parked; however, the amount of fuel that leaked from the airplane could not be determined.
The pilot aborted the first takeoff shortly after becoming airborne. Although he did not state why he aborted the takeoff, he told the tower controller that he did not need assistance; shortly thereafter, he requested and was cleared for a second takeoff. During the initial climb, the pilot declared an emergency and was cleared to land on any runway. Witnesses reported that the airplane was between 400 ft and 800 ft above the ground in a left bank and appeared to be turning back to land on an intersecting runway. They thought the airplane was going to make it back to the runway, but the airplane's bank angle increased past 90° and the nose suddenly dropped; the airplane subsequently impacted terrain. One of the pilots likened the maneuver to a stall/spin, Vmc roll, or snap roll.
Examination of the flight controls and engines did not reveal any anomalies that would have prevented normal operation. The position of the fuel valves was consistent with the fuel being shut off to the left engine. The fuel valves, with the exception of the left main valve, functioned when power was applied. The left main valve was intact, but the motor was found to operate intermittently. The amount of fuel found in the left engine injection servo was less than that in the right engine; however, the cylinder head temperatures and exhaust gas temperatures were consistent between both engines for the duration of the flight, and whether or to what extent the left engine may have experienced a loss of power could not be determined.
The available evidence was insufficient to determine why the pilot declared an emergency and elected to return to the airport; however, the airplane's increased left bank and nose-down attitude just before impact is consistent with a loss of control.
Probable cause
The pilot's loss of control while returning to the airport after takeoff for reasons that could not be determined based on the available information.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN18FA050
- Event ID
- 20171210X70535
- Case number
- CEN18FA050
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 862f3760e0c78ad0f92b65666d93f5418ce461a9d33db1504ac11591c62dcb8c; retrieved 2026-09-15T06:27:07.204Z.