LAX99LA174 · Cessna T303
Cessna T303 · Accident: total loss of engine power (non-mechanical) on approach
From Sugar Land Regional Airport (SGR) to San Diego International Airport (SAN)
Event
- NTSB case
- LAX99LA174
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna T303
- Aircraft type
- Cessna 303
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N3303S
- Operator
- Neville A. Lewis · private individual
- Onboard fatalities
- Unknown
- Route
- From Sugar Land Regional Airport (SGR), SUGAR LAND MUNI, TXTo San Diego International Airport (SAN)
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · IFR missed approach
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Total loss of engine power (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel exhaustion
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Fuel consumption calculations, inaccurate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane departed Houston, Texas, for a VFR flight to San Diego, California. The pilot in the left seat said that they originally planned to purchase fuel at Gila Bend, Arizona, but were told that the fueling was closed. The left seat pilot said they elected to land at a private airstrip and made arrangements to have an individual drive to Casa Grande airport to purchase fuel for them. The left seat pilot said they were worried about adequate runway length, so they elected to only purchase 65 gallons of fuel for the remainder of the flight to San Diego. En route to San Diego, the right seat pilot obtained weather for the destination from FSS and was advised of 1,000-foot overcast ceiling. The right seat pilot then requested and received an instrument clearance. The TRACON controller advised the pilot of the accident airplane that he would have to keep speed up due to jet traffic or be given delay vectors for traffic spacing. The pilot told ATC that they were fuel critical and later said they had about 45 minutes to 1 hour of fuel. The right seat pilot was cleared for the localizer runway 27 approach. Approximately 18 minutes later, the pilot elected to do a missed approach because he was too high to land and moments later told San Diego radar that he was fuel critical and only had about 5 minutes of fuel left. San Diego radar began to give the pilot vectors to the closest airport and told the pilot not to descend any further. The right seat pilot replied that they were a glider and later told San Diego police that they had run out of fuel. There were no discrepancies noted with either the airframe or the engines during the postaccident aircraft examination.
Probable cause
The pilot-in-command's inaccurate fuel consumption calculations that resulted in fuel exhaustion and the subsequent ditching.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX99LA174
- Event ID
- 20001212X18805
- Case number
- LAX99LA174
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1999-05-08.
- API snapshot SHA-256: da7797c4c9bc96006f3ca3e05581c17e19f4fd6ea2343b051daa88a14c062478; retrieved 2026-09-22T15:18:02.862Z.