# Incident 20120507011549I: Piper PA-32-300, Tinian, CM, May 7, 2012

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 7, 2012, 16:05 local time
- Place: Tinian, CM
- Airport: Tinian International
- Damage: Minor damage
- Phase of flight: Takeoff: Climb Out
- Operating rules: Air taxi and commuter (Part 135)
- Operator: 1SMA
- Aircraft: N4127R, registered now (https://openairdocs.org/aircraft/N4127R) (OpenAirDocs)
- Registry model: Piper PA-32-300 (registry code 7103212, https://openairdocs.org/model/piper-pa-32-300) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA-32-300
- Reported engine: LYCOMING TI0-540 SER
- People aboard: 6
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor, private pilot
- Pilot flight hours: 526 total, 78 in this make and model, 78 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20120507011549I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

PIC PLACED FUEL SELECTOR ON AN OUTBOARD TANK THAT CONTAINED MINIMUM FUEL. DURING TAKEOFF ENGINE LOST POWER THAT REQUIRED A LANDING ON THE REMAINING RUNWAY. PIC INDICATED TO MANAGEMENT HE DID NOT VISUALLY CHECK AMOUNT OF FUEL IN TANK PRIOR TO DEPARTURE.

## Other reports on N4127R (2)

Matched to the same aircraft by N-number and date.

- [Incident 19880704036009I](https://openairdocs.org/incident/19880704036009I), Jul 4, 1988: Piper PA32300 (N4127R), Plain City, UT. Parachute jumper hit a baseball field fence on landing. Caused minor injury.
- [Accident 19800201001959A](https://openairdocs.org/incident/19800201001959A), Feb 1, 1980: Piper PA32300 (N4127R), Festus, MO, Substantial damage. Instructor allowed aircraft to develop high sink rate on final. Tried to salvage landing but impacted runway.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.