# Incident 19970220008069I: Piper PA34200, Long Beach, CA, February 20, 1997

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 20, 1997, 17:30 local time
- Place: Long Beach, CA
- Airport: Long Beach - Daugherty Field
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 33.7670° N, 118.1892° W: Placed by OpenAirDocs: center of Long Beach, CA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.7670&lon=-118.1892&mi=10
- Aircraft: N56484, a cancelled registration (https://openairdocs.org/deregistered/N56484-2013-09-24) (OpenAirDocs)
- Registry model: Piper PA-34-200 (registry code 7103405, https://openairdocs.org/model/piper-pa-34-200) (OpenAirDocs)
- Registry engine: Lycoming I0360 SER A&C (registry code 41511, https://openairdocs.org/engine/lycoming-i0360-ser-a-c) (OpenAirDocs)
- Reported make and model: PIPER PA34200
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 2,390 total, 500 in this make and model, 200 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19970220008069I

## Narrative

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

NARRATIVE: THIS INCIDENT OCCURRED DURING A FLIGHT INSTRUCTION SESSION. THE FLIGHT INSTRUCTOR, MR. TABASSIAN STATED THAT HE AND HIS STUDENT HAD COMPLETED AIR WORK AT 3500 MSL AND HAD RETURNED TO THE LONG BEACH AIRPORT FOR TOUCH AND GOS PRIOR TO RETURNING TO VNY. THE LONG BEACH ATCT CLEARED THE AIRPLANE INTO THE TRAFFIC PATTERN AND THEN FOR A TOUCH AND GO. ON SHORT FINAL THE INSTRUCTOR VERIFIED THAT HE SAW "3 GREEN" LIGHTS. ALL OTHER INDICATIONS SUCH AS SOUND WERE NORMAL INDICATING THAT THE GEAR WAS DOWN AND LOCKED. ON LANDING THE NOSE OF THE AIRCRAFT "KEPT GOING DOWN" UNTIL IT IMPACTED THE GROUND. ACCORDING TO THE FLIGHT INSTRUCTOR, NO SPECIFIC CAUSE OF THE FAILURE WAS FOUND DURING POST-INCIDENT INSPECTION AND REPAIR. CASE CLOSED.

## Other reports on N56484 (4)

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

- [Accident 20030111000509A](https://openairdocs.org/incident/20030111000509A), Jan 11, 2003: Piper PA34200 (N56484), Westlakevillage, CA, Destroyed. (.19) On January 11, 2003, at 1023 pacific standard time, a Piper PA-34-200, N56484, made a forced landing in westlake village, California, following a loss of…
- [Incident 19960426018319I](https://openairdocs.org/incident/19960426018319I), Apr 26, 1996: Piper PA34200 (N56484), Van Nuys, CA, Minor damage. Narrative: just before touchdown, the instructor asked the student, "3 greens, yes?" And then visually looked at the 3 green landing gear down lights himself,…
- [Accident 19950624047209A](https://openairdocs.org/incident/19950624047209A), Jun 24, 1995: Piper PA34200 (N56484), Avalon, CA, Substantial damage. Brakes failed landing. Overran runway into fence. First flight since brakes replaced had air in lines.
- [Incident 19920815037359I](https://openairdocs.org/incident/19920815037359I), Aug 15, 1992: Piper PA34200 (N56484), Los Angeles, CA, Minor damage. Nose landing gear collapsed on landing rollout.

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.