# Incident 20180410000729I: Piper PA-34-200, San Diego, CA, April 10, 2018

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: April 10, 2018, 14:03 local time
- Place: San Diego, CA
- Airport: Brown Field
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 32.5725° N, 116.9806° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=32.5725&lon=-116.9806&mi=10
- Aircraft: N4567T, registered now (https://openairdocs.org/aircraft/N4567T) (OpenAirDocs)
- Registry model: Piper PA-34-200 (registry code 7103405, https://openairdocs.org/model/piper-pa-34-200) (OpenAirDocs)
- Registry engine: Lycoming I0360 series (registry code 41515, https://openairdocs.org/engine/lycoming-i0360-series) (OpenAirDocs)
- Reported make and model: PIPER PA-34-200
- Reported engine: LYCOMING I0360 SER
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport, commercial pilot, flight instructor
- Pilot flight hours: 5,000 total, 800 in this make and model, 34 in the last 90 days
- NTSB investigation: [NTSB GAA18CA207](https://openairdocs.org/ntsb/GAA18CA207) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20180410000729I

## Narrative

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

THIS WAS A PRACTICE MULTI -ENGINE STOP AND GO LANDING / PATTERN WORK. THE FOURTH LANDING WAS A SIMULATED ENGINE OUT SINGLE ENGINE APPROACH.THE INSTRUCTOR BECAME DISTRACTED WITH DISCUSSION AND PROCEDURES FOR THIS TYPE OF LANDING AND DID NOT VERIFY THAT THE GEAR WAS DOWN AND LOCKED. THE AIRCRAFT LANDED IN A GEAR UP CONFIGURATION.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB GAA18CA207](https://openairdocs.org/ntsb/GAA18CA207), Apr 10, 2018: Piper PA34 (N4567T), San Diego, CA, substantial damage. Probable cause: The pilot receiving instruction and flight instructor’s failure to properly configure the landing gear before landing, which resulted in landing with the landing gear retracted.

## Other reports on N4567T (3)

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

- [Incident 20210906015429I](https://openairdocs.org/incident/20210906015429I), Sep 6, 2021: Piper PA-34-200 (N4567T), San Diego, CA, Minor damage. On September 6, 2021, around 14:10 PDT, N4567T nose gear collapsed while taxing off the active runway after landing.
- [Incident 20040222004629I](https://openairdocs.org/incident/20040222004629I), Feb 22, 2004: Piper PA34200 (N4567T), Fort Worth, TX, Minor damage. (-23) On February 22, 2004, at 1930 CDT, a Piper seneca PA-34-200, N4567T, owned by eagle eye aviation, inc. of venus, TX., had an incident upon landing at…
- [Incident 19830127009379I](https://openairdocs.org/incident/19830127009379I), Jan 27, 1983: Piper PA34200 (N4567T), Shelby, MT, Minor damage. Instructor allowed student to make hard landing. Impact collpased nose gear.

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.