FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA02FAMS3 · Piper PA-36-300

6 Sept 2002 · Missing, United States

Piper PA-36-300 · Accident: missing aircraft

From Fort Lauderdale Executive Airport (KFXE) to Henry E. Rohlsen Airport (TISX)

Report a problem

Event

NTSB case
MIA02FAMS3
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
Not recorded

Piper PA-36-300

Aircraft type
Piper PA-36
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
N59684
Operator
Jose B. Arruda · private individual
Onboard fatalities
Unknown
Route
From Fort Lauderdale Executive Airport (KFXE), Fort Lauderdale, FLTo Henry E. Rohlsen Airport (TISX), St. Croix
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
Unknown
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
Missing aircraft
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

  • Reason for occurrence undetermined

Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.

NTSB narrative

The agricultural airplane was converted by an unknown person to supply fuel from the 38 cubic foot hopper tank, to the right fuel tank. Additionally, the pilot reportedly carried a fully charged 12-volt battery and an electrically operated artificial horizon with him on the accident flight as the agricultural airplane did not have an artificial horizon installed. The day before the accident, the pilot fueled the hopper tank, and a lineservice person filled both wing fuel tanks. There was no record that the pilot obtained a preflight weather briefing either through an FAA Automated Flight Service Station, or through the DUAT vendors. The flight departed at 0727, and after takeoff air traffic control communications were transferred from the Fort Lauderdale Executive Air Traffic Control Tower to the Fort Lauderdale International Air Traffic Control (ATC) Tower. The flight remained in contact with that facility from 0731:00 to 0732:10. The next recorded air traffic control communications occurred at 0852:30, when the pilot contacted Nassau Approach Control advising that the flight was at 1,500 feet and 40 miles northwest of Nassau, en route from Fort Lauderdale, to St. Croix. The controller provided the pilot a discrete transponder code, then radar identified the flight advising the pilot that the flight was 35 miles west of Nassau. The pilot then advised the controller that he would be maintaining 1,500 feet, to which the controller advised the flight would not be able to proceed overhead due to the altitude flown, and provided a heading to fly until the flight was abeam Nassau. After that time, the pilot could proceed on-course. At 0928:03, the controller advised the pilot of the altitude and location of traffic, and to, "...resume normal navigation to your destination." The pilot acknowledged that comment and the controller terminated radar services at 0932:58. There were no further contacts reported with any ATC facilities along the route of flight. According to the controller who handled the communications with the accident pilot, the flight was vectored about 10 nautical miles southwest of Nassau for traffic and weather. The flight was then vectored approximately 20 miles to the southeast of Nassau, where radar services were terminated, the airplane was clear of traffic and weather, and the airplane was proceeding southeast bound. The Nassau radar data is not recorded; therefore, a radar plot is not available. Review of the chronological notes from the U.S. Coast Guard, revealed the Coast Guard (CG) was first notified of the missing airplane by the Air Force Rescue Coordination Center (AFRCC), on September 8, 2002, at 1420. The CG initiated a communications search and also performed a track line search on September 12, 2002, from the last known position to Providenciales. The results were negative. According to the NTSB Weather Study, at the time of the last known position located approximately 20 nautical miles southeast of Nassau (0932), an infrared satellite image indicates a band of high clouds with embedded cumulonimbus clouds extending south of a line from Ft. Lauderdale, and Nassau, southeastward towards the Virgin Islands. The last known position was located on the leading edge of higher cloud cover with tops to 38,000 feet. Additionally, enhanced cloud developement with tops to 44,000 feet was noted at a point located 38 miles south of the last known position. According to the pilot's daughter, her father was ferrying the airplane for the new owner to Brazil. She reported that her father had on-board a GPS, a 4 man life raft, and a life jacket that he always wore. He also had a survival kit and a satellite cellular phone, which was tested the day before the accident. Her father has been ferrying airplanes to Brazil for approximately 7 years, and advised her that he would call her using his satellite phone when flying over Providenciales; she was not contacted by her father.

Probable cause

The falure of the pilot to arrive at the intended destination for undetermined reasons. A finding in the investigation was the fact that clouds with tops to 44,000 feet were noted 38 miles south of the airplane's last position.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA02FAMS3
Event ID
20020920X05185
Case number
MIA02FAMS3
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: 5c00fedc3fe0c06808b3752c92dd2a156011da7f9424e69c895ae9754529abd4; retrieved 2026-09-20T19:52:57.334Z.