# Accident 20100824042091A: Cessna 150J, Sequim, WA, August 24, 2010

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 24, 2010, 16:12 local time
- Place: Sequim, WA
- Airport: Diamond Point Airstrip
- Damage: Substantial damage
- Collision: Collision on the ground
- Phase of flight: Run-Up Area
- Operating rules: General operating rules (Part 91)
- Location: 48.0903° N, 122.9244° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=48.0903&lon=-122.9244&mi=10
- Aircraft: N50464, a cancelled registration (https://openairdocs.org/deregistered/N50464-2014-11-25) (OpenAirDocs)
- Registry model: Cessna 150J (registry code 2071820, https://openairdocs.org/model/cessna-150j) (OpenAirDocs)
- Registry engine: Continental 0-200 series (registry code 17020, https://openairdocs.org/engine/continental-0-200-series) (OpenAirDocs)
- Reported make and model: CESSNA 150J
- Reported engine: CONT MOTOR 0-200 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot flight hours: 0 total, 0 in this make and model, 0 in the last 90 days
- NTSB investigation: [NTSB WPR10LA427](https://openairdocs.org/ntsb/WPR10LA427) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20100824042091A

## Narrative

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

THE AIRCRAFT WAS IN THE RUNUP AREA NEXT TO THE RUNWAY.  AN AIRCRAFT COMING IN TO LAND TOUCHED PRIOR TO THE RUNWAY AND BOUNCED, STRIKING THE AIRCRAFT IN HE RUNUP AREA.

## 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 WPR10LA427](https://openairdocs.org/ntsb/WPR10LA427), Aug 24, 2010: Cessna 150J (N50464), Sequim, WA, substantial damage. Probable cause: The pilot’s failure to maintain the proper approach path and his delayed corrective actions, which resulted in an undershoot. Contributing to the accident was the pilot's distraction from other…

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.