# Incident 19990119019799I: Cessna 150J, Indio, CA, January 19, 1999

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 19, 1999, 13:00 local time
- Place: Indio, CA
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 33.7206° N, 116.2156° W: Placed by OpenAirDocs: center of Indio, CA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.7206&lon=-116.2156&mi=10
- Aircraft: N61233, registered now (https://openairdocs.org/aircraft/N61233) (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
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 1,015 total, 30 in this make and model, 12 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19990119019799I

## Narrative

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

ON JANUARY 19, 1999, AT 10:50 A.M. PACIFIC DAYLIGHT TIME, A CESSNA 150, N61233, DEPARTED PHOENIX AZ, WITH 1 PASSENGER ON BOARD FOR A VFR FLIGHT TO SANTA ANA CA. APPROXIMATELY 3 HRS AND 20 MIN. INTO THE FLIGHT, THE PILOT CONTACTED PALM SPRINGS APPROACH CONTROL AND STATED THAT HE WAS WESTBOUND OVER THE INTERSTATE 10 FREEWAY AND HAD A ROUGH RUNNING ENGINE.  THE CONTROLLER ADVISED THE PILOT OF HIS POSITION RELATIVE TO BURMUDA DUNES AIRPORT AND SUGGESTED THAT HE REMAIN OVER THE FREEWAY UNTIL SUCH TIME AS HE REACHED THE AIRPORT FOR A PRECAUTIONARY LANDING.  THE AIRCRAFT WAS LANDED POWER OFF ON THE 10 FREEWAY APPROX. 5 MILES EAST OF THE BERMUDA DUNES AIRPORT.  THERE WERE NO INJURIES TO THE OCCUPANTS OR DAMAGE TO THE AIRCRAFT.  FOLLOWING THE LANDING, THE PILOT CONTACTED THE PALM SPRINGS TOWER AND TOLD THE CONTROLLER THAT THE AIRCRAFT HAD APPARENTLY RUN OUT OF FUEL.  DURING AN INTERVIEW WITH THE PILOT, HE STATED THAT HE FILED A VFR FLIGHT PLAN WITH PRESCOTT FLIGHT SERVICE AND RECEIVED A STANDARD PILOT WEATHER BRIEFING.  THE PILOT STATED THAT PRIOR TO DEPARTING PHOENIX, THE AIRCRAFT WAS FUELED TO CAPACITY.  HE STATED THAT BASED ON HIS PLANNED CRUSE ALTITUDE, POWER SETTING, AND FULL FUEL TAN KS, THE AIRCRAFT'S PILOT OPERATING HANDBOOK INDICATES THE AIRCRAFT SHOULD HAVE REMAINED ALOFT FOR 4 HRS. AND 20 MINUTES. THIS WAS BY HIS PLANNING, SUFFICIENT TIME TO REACH HIS PLANNED FUEL STOP, PALM SPRINGS, WITH A 30-MINUTE RESERVE.

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.