FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA03FA025 · Raytheon 58

6 Dec 2002 · Fort Myers, FL, United States

Raytheon 58 · Accident: loss of control in flight on approach

From OA8 · Centerville, AL to Naples Municipal Airport (APF)

Report a problem

Event

NTSB case
MIA03FA025
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
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
Instrument Meteorological Cond

Raytheon 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
N241JG
Operator
Laurence G. Casey · private individual
Onboard fatalities
Unknown
Route
From OA8 · Centerville, ALTo Naples Municipal Airport (APF), Naples, FL
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
Approach · IFR missed approach
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 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

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › Spatial disorientation

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

NTSB narrative

The twin-engine airplane impacted a residential area after a loss of aircraft control during a missed approach in instrument meteorological conditions (IMC). The flight departed Alabama and made its way to Florida uneventfully where it made a non-precision approach at Naples with 500-foot ceilings and a visibility of two statute miles in mist. The pilot executed a missed approach after descending to the minimum descent altitude of 500 feet. After conducting the missed approach, the pilot requested to divert to Fort Meyers where they had a precision approach. Fort Meyers was reporting 300-foot ceilings and 3 statute miles of visibility at the time of the accident. The pilot conducted three approaches to Fort Meyers. The pilot was unable to obtain/maintain the final approach course and conducted a teardrop course reversal on the first two approaches to Fort Meyers before reaching the final approach fix. The pilot indicated he was experiencing "very big difficulties out here" and mentioned instrument problems, but was going to try to fly the next approach manually. The controller asked the pilot about his fuel status, to which the pilot reported it was in the yellow range. When the controller asked how much time that was, the pilot responded it was "practically nil." The controller then set the pilot up for another precision approach attempt and eventually converted it to a surveillance approach when it became apparent the pilot was having trouble obtaining and maintaining the final approach course. The airplane's radar track was over the final approach course during the final approach attempt; however, the airplane's minimum altitude was 300 feet over the approach end of the runway. The airplane overflew the runway and began a climb to 600 feet. The airplane then descended to 300 feet again as it began a left turn. The controller instructed the pilot to climb and maintain 1,500 feet and provided two vectors, neither of which the aircraft followed. The maximum altitude the airplane attained during the last missed approach was 1,200 feet before it began its final, uncontrolled descent. The last communication obtained from the pilot was during the initiation of the missed approach. The airplane departed controlled flight and impacted a garage and terrain. Wreckage was strewn 350 feet. The airplane was observed descending out of the clouds heading south at a low altitude, with the landing gear retracted, full power and a high rate of speed. Additional witnesses heard engine noise emanating from the airplane prior to both engines going silent. The propellers separated from the engines and the engines separated from the airplane. The right engine proceeded through another house before coming to rest in its attic. Post-accident examination of the engines' throttle bodies and fuel metering units revealed that the right fuel metering unit fuel flows were in excess of those specified by the manufacturer. The left fuel metering unit was substantially damaged and could not be flow tested. No additional pre-impact anomalies were noted with the airframe, its engines, or propellers that would have precluded their normal operation. The damage sustained by the cockpit was enough to preclude functional testing of any of the navigation equipment and instruments. The accident flight lasted 3 hours and 21 minutes and the pilot's flight plan indicated he had about 4 hours and 15 minutes of fuel on board. The left fuel selector was found in the ON position and the right fuel selector was found in the OFF position.

Probable cause

the pilot's spatial disorientation during instrument meteorological conditions, which resulted in his failure to maintain aircraft control. Contributing factors included the pilot's distraction to the low fuel status and the low cloud conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA03FA025
Event ID
20021212X05598
Case number
MIA03FA025
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: 007e7dabb100d203c29ae3950cbc4a774299f3575daf1645b52a7ff253bcff78; retrieved 2026-09-20T19:35:29.000Z.