# Accident 19940311005059A: Cessna 172P, Seattle, WA, March 11, 1994

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 11, 1994, 13:00 local time
- Place: Seattle, WA
- Airport: Boeing Field-King County International
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Operator: GJAV
- Location: 47.6703° N, 122.3801° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=47.6703&lon=-122.3801&mi=10
- Aircraft: N52807, a cancelled registration (https://openairdocs.org/deregistered/N52807-2009-07-28) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 674 total, 201 in this make and model, 65 in the last 90 days
- NTSB investigation: [NTSB SEA94LA083](https://openairdocs.org/ntsb/SEA94LA083) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19940311005059A

## Narrative

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

STUDENT FAILED TO FLARE PROPERLY FOR LANDING. CFI FAILED TO CORRECT OR PREVENT LACK OF FLARE.

## 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 SEA94LA083](https://openairdocs.org/ntsb/SEA94LA083), Mar 11, 1994: Cessna 172 (N52807), Seattle, WA, substantial damage. Probable cause: THE STUDENT'S IMPROPER FLARE FOR LANDING AND THE INSTRUCTOR'S DELAYED REMEDIAL ACTION.

## Other reports on N52807 (4)

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

- [Accident 20080604838349A](https://openairdocs.org/incident/20080604838349A), Jun 4, 2008: Cessna 172P (N52807), Bremerton, WA, Substantial damage. (-23) The student pilot was attempting to make his second landing on runway 01 at the Bremerton airport (kpwt) on his first solo flight. The aircraft bounced…
- [Incident 20000821023769I](https://openairdocs.org/incident/20000821023769I), Aug 21, 2000: Cessna 172P (N52807), Seattle, WA, Minor damage. (-23)Student on solo. Noticed red light at rotation. Student landed aircraft straight ahead and used heavy breaking, causing both main tires to deflate.…
- [Incident 19900809051169I](https://openairdocs.org/incident/19900809051169I), Aug 9, 1990: Cessna 172P (N52807), Portland, OR. Lost electrical power. Diverted for landing. Overflew once and landed. Alternator faulty.
- [Accident 19830405014509A](https://openairdocs.org/incident/19830405014509A), Apr 5, 1983: Cessna 172P (N52807), Snohomish, WA, Substantial damage. Pilot landed airplane on last third of runway and rolled off the end, struck a ditch and flipped inverted.

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.