# Accident 19960310003719A: Cessna 150M, Muleshoe, TX, March 10, 1996

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 10, 1996
- Place: Muleshoe, TX
- Damage: Destroyed
- Location: 34.2197° N, 102.7197° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=34.2197&lon=-102.7197&mi=10
- Aircraft: N66362, a cancelled registration (https://openairdocs.org/deregistered/N66362-1997-08-18) (OpenAirDocs)
- Registry model: Cessna 150M (registry code 2071830, https://openairdocs.org/model/cessna-150m) (OpenAirDocs)
- Reported make and model: CESSNA 150M
- People aboard: 1
- Fatal injuries: 1
- NTSB investigation: [NTSB FTW96FA143](https://openairdocs.org/ntsb/FTW96FA143) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19960310003719A

## Narrative

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

BECAME LOST, SAW A AIRPORT, TRIED TO LAND. HAD NOT MADE CONTACT WITH TOWER.

## 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 FTW96FA143](https://openairdocs.org/ntsb/FTW96FA143), Mar 10, 1996: Cessna 150 (N66362), Muleshoe, TX, destroyed, 1 fatal. Probable cause: improper planning/decision by the student pilot, and his failure to take adequate remedial action after becoming lost and encountering a low fuel situation, which subsequently resulted in fuel…

## Other reports on N66362 (1)

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

- [Incident 19930627028649I](https://openairdocs.org/incident/19930627028649I), Jun 27, 1993: Cessna 150M (N66362), Gainesville, TX, Minor damage. Engine quit on crosscountry flight due to fuel exhaustion. Forced landing at Gainesville. Struck a fence on approach

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.