# Accident 20020328004189A: Cessna 150M, Salisburycenter, NY, March 28, 2002

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 28, 2002, 17:10 local time
- Place: Salisburycenter, NY
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 43.2792° N, 74.7992° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=43.2792&lon=-74.7992&mi=10
- Aircraft: N3006V, a cancelled registration (https://openairdocs.org/deregistered/N3006V-2002-06-17) (OpenAirDocs)
- Registry model: Cessna 150M (registry code 2071830, https://openairdocs.org/model/cessna-150m) (OpenAirDocs)
- Registry engine: Continental 0-200 series (registry code 17020, https://openairdocs.org/engine/continental-0-200-series) (OpenAirDocs)
- Reported make and model: CESSNA 150M
- NTSB investigation: [NTSB NYC02LA078](https://openairdocs.org/ntsb/NYC02LA078) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020328004189A

## Narrative

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

(-23) AIRCRAFT DEPARTED HAMILTON, NY (B24), FLEW TOWARD ELMYRA, NY, AND TURNED TO RETURN TO HAMILTON, NY. PILOT WAS CONFUSED AND TURNED SOUTH, TO THE BINGHAMTON VOR TO THE ROCKDALE VOR, TRYING TO FIND HAMILTON, NY. THE PILOT DIALED "030" INSTEAD OF "330" ON THE VOR AND FLEW NORTHEAST BOUND, GOT LOST, RAN LOW ON GAS, REPORTED A ROUGH RUNNING ENGINE, DECLARED AN EMERGENCY WITH BUFFALO FFS, AND CRASHED IN THE WET LANDS NORTH OF SALISBURY CENTER, NY.

## 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 NYC02LA078](https://openairdocs.org/ntsb/NYC02LA078), Mar 28, 2002: Cessna 150M (N3006V), Salisbury Ctr, NY, substantial damage. Probable cause: The pilot's delayed decision to ask for help which led to a power loss due to fuel starvation.

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.