FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight 484 · Beech 58

17 Jul 2000 · Hernando, MS, United States

Beech 58 · Accident: airframe, component or system failure en route

From Frederick W. Smith International Airport (KMEM) to William P. Hobby Airport (KHOU)

Report a problem

Event

NTSB case
MIA00FA221
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
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
Visual Meteorological Cond

Beech 58

Aircraft type
Beechcraft 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
N158MT
Operator
Unknown
Onboard fatalities
Unknown
Route
From Frederick W. Smith International Airport (KMEM), Memphis, TNTo William P. Hobby Airport (KHOU), Houston, TX
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
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
Destroyed

Cause areas

  • Pilot in command › Checklist, not followed

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Approximately 7 minutes after the flight departed while flying at 6,000 feet mean sea level (msl), the pilot radioed the controller advising, "star check four eighty four we're gonna shut the master switch off we've got a electrical fire." The controller asked the pilot to repeat the transmission to which he again reported he was going to shut off the master switch. The controller advised the pilot of the location of a nearby airport to which the pilot replied, "standby." Approximately 20 seconds after the pilot first advised the controller of an electrical fire, the pilot declared an emergency and advised the controller the flight was descending. The controller advised the pilot of a nearby grass airstrip to which the pilot questioned the location and, "...we need to land immediately." The controller again advised the pilot of the location of the grass strip; there were no further communications from the accident pilot. Witnesses located near the accident site reported seeing smoke or what was described as "vapor trail" or "dust" trailing the airplane before it impacted the water on Arkabutla Lake. Radar data indicates transponder beacon returns continue every 4.6 seconds when reviewed in 1-minute increments beginning at 1154:06, until 1201:54, when the last transponder beacon return indicated the airplane was at 5,400 feet msl. A primary uncorrelated radar return was observed in close proximity to the last correlated transponder return, and continue approximately every 4-5 seconds until 1203:31. Review of the primary radar returns revealed between 1201:59, and 1203:21, the target was noted to bank to the left from a southerly heading to a northeasterly heading; the final two uncorrelated radar returns indicates the airplane banked to the right where the last return was noted over a section of Arkabutla Lake. Before recovery of the airplane, a section of the horizontal stabilizer was noted above the surface of the water. The right wing and cockpit from the forward carry-thru spar forward were fragmented. The left wing was separated but comprised of mainly 1 piece. Examination of the cockpit revealed heat damage was localized on the pilot's side of the airplane behind the instrument panel. The battery switch was found in the off position while both alternator switches were found in the on position. A 10-gauge electrical wire which acts as a jumper between the W15 and W11 bus bars on the left hand subpanel was fractured and exhibited evidence of arching on the supply side wire. The surface of a pilot air control located in the area of the arched 10-gauge wire exhibited arching damage on the surface which was comprised in part of tin. Tin was not detected on the undamaged area of the pilot air control. The damaged 10-gauge wire was noted to be comprised in part of tin. A rigid aluminum line for the left fuel flow and pressure indicator gauge was noted to be cracked, sooted, and bulged in the area on the pilot's side of the instrument panel near the combination oil pressure/oil temperature/cylinder temperature gauge. The line exhibited features associated with overstress fracture at an elevated temperature. A rigid aluminum line for left oil pressure was noted to have a section missing; the line exhibited features associated with overstress fracture at an elevated temperature. Post accident testing to duplicate the as-found condition of the 10-gauge wire revealed the large ball on the end of the accident wire could be duplicated when a compressive load was applied to the 10-gauge wire shorting it to ground, and current from the batteries supplying current to the 10-gauge wire. Additional post accident testing of current limiters with various loads applied revealed the current limiters opened at decreasing times with an increase in current applied. Review of the emergency checklist for the airplane pertaining to electrical smoke or fire revealed a pilot is directed to shut off the battery and both alternator switches.

Probable cause

The arcing of an electrical wire behind the instrument panel and the associated cracking of fuel and oil lines. Also causal was the pilot's inappropriate remedial action not in accordance with the emergency checklist.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA00FA221
Event ID
20001212X21532
Case number
MIA00FA221
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: d789a357760ab12669940f67c356df9c7c9a5777fbb4ab729b5d4d285325c797; retrieved 2026-09-18T13:12:21.617Z.