What happened
On June 8, 2019, a Piper PA-34 200T, registration PR-PPL, departed from Aeródromo Fazenda Santa Fé in Iranduba, Amazonas, for a repositioning flight to Flores, Amazonas. The flight was being conducted as a private operation with a pilot and one passenger on board.
As the aircraft approached its destination, the pilot reported a simultaneous failure of both engines. In response to the loss of power, the pilot performed an emergency landing on the Rio Negro. Following the impact with the water, the aircraft submerged to a depth of approximately 50 meters. The occupants managed to abandon the aircraft through the main door and were rescued by a local resident in a nearby boat. The pilot escaped uninjured, while the passenger sustained minor injuries.
The investigation
CENIPA investigators examined the aircraft's maintenance history and flight records. While the pilot held valid commercial licenses and medical certification, and the aircraft possessed a valid Certificate of Airworthiness, significant discrepancies were found in the technical logs.
An audit of the airframe, engine, and propeller logbooks revealed inconsistent flight hour totals, with some entries showing fewer hours than previous inspections. Furthermore, investigators identified conflicting data between the aircraft's physical maintenance records and the ANAC (National Civil Aviation Agency) digital database regarding the date and location of the last annual inspection. Because the aircraft remained submerged due to high river levels, a physical examination of the engines and systems could not be performed at the time of the accident.
Findings
- The pilot was properly qualified and rated for multi-engine instrument flight.
- Weather conditions at the time of the accident were suitable for visual flight.
- The aircraft had sufficient fuel for the planned flight duration.
- Inconsistent maintenance records prevented investigators from verifying the actual airworthiness status of the engines and airframe.
- The maintenance quality of the operator's organization was called into question due to the identified clerical errors and data discrepancies.