# Accident 20031229035309A: Cessna 210, Rialto, CA, December 29, 2003 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: December 29, 2003, 23:10 local time - Place: Rialto, CA - Damage: Substantial damage - Phase of flight: Fcd/Prec Ldg From Cruise - Operating rules: General operating rules (Part 91) - Location: 34.1317° N, 117.4025° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=34.1317&lon=-117.4025&mi=10 - Aircraft: N6539X, a cancelled registration (https://openairdocs.org/deregistered/N6539X-2013-04-30) (OpenAirDocs) - Registry model: Cessna 210 (registry code 2073402, https://openairdocs.org/model/cessna-210) (OpenAirDocs) - Registry engine: Continental I0-470 series (registry code 17027, https://openairdocs.org/engine/continental-i0-470-series) (OpenAirDocs) - Reported make and model: CESSNA 210 - Reported engine: CONT IO470* - People aboard: 1 - Fatal injuries: 0 - Pilot flight hours: 15,000 total, 800 in this make and model, 60 in the last 90 days - NTSB investigation: [NTSB LAX04LA083](https://openairdocs.org/ntsb/LAX04LA083) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20031229035309A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (-23) ON DECEMBER 29, 2003, AT 2319 PACIFIC STANDARD TIME, A CESSNA 210, N6539X, COLLIDED WITH GROUND OBSTACLES FOLLOWING A LOSS OF ENGINE POWER DURING A VFR GO AROUND FROM RUNWAY 24 AT THE RIALTO, CALIFORNIA, AIRPORT. THE AIRCRAFT WAS OWNED AND OPERATED BY A PRIVATE INDIVIDUAL, WHO WAS THE PASSENGER ON THIS FLIGHT, UNDER THE PROVISIONS OF 14 CFR PART 91 OF THE FEDERAL AVIATION REGULATIONS. THE AIRPLANE SUSTAINED SUBSTANTIAL DAMAGE. THE AIRLINE TRANSPORT PILOT AND THE ONE PASSENGER ON BOARD SUSTAINED MINOR INJURIES. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AND AN IFR FLIGHT PLAN WAS FILED FOR THE PERSONAL CROSS-COUNTRY FLIGHT THAT ORIGINATED AT THE NORTH LAS VEGAS, NEVADA, AIRPORT ABOUT 2130, AND WAS EN ROUTE TO CHINO, CALIFORNIA. ACCORDING TO INFORMATION PROVIDED BY THE FEDERAL AVIATION ADMINISTRATION (FAA), THE FLIGHT WAS LEVEL AT 8,000 FEET OPERATING ON AN INSTRUMENT CLEARANCE WHEN THE PILOT TOLD AIR TRAFFIC CONTROL THAT THE AIRPLANE "WAS LOSING FUEL" AND HE WISHED TO DECLARE AND EMERGENCY, ADDING THAT HE NEEDED TO LAND AT THE CLOSEST AIRPORT. THE SOUTHERN CALIFORNIA TRACON SECTOR CONTROLLER WORKING THE FLIGHT POINTED OUT THREE AIRPORTS AND THE PILOT ELECTED TO LAND AT RIALTO.THE CONTROLLER CLEARED THE FLIGHT TO DO SO. RIALTO POLICE OFFICERS RESPONDED TO THE ACCIDENT SITE. ACCORDING TO THE ON SCENE INCIDENT COMMANDER, THE PILOT TOLD THE OFFICERS THAT HE HAD SOMEHOW "RAN OUT OF GAS" AT 8,000 FEET OVER THE AIRPORT. HE FURTHER TOLD THE OFFICERS THAT HE DID NOT UNDERSTAND HOW THIS HAPPENED SINCE THE FUEL TANKS HAD BEEN FILLED PRIOR TO LEAVING LAS VEGAS. THE PILOT REPORTED THAT HE HAD SPIRALED DOWN OVER THE AIRPORT AND HAD SETUP TO LAND ON RUNWAY 24. THE AIRPLANE THEN IMPACTED A CHAIN LINK FENCE OFF THE DEPARTURE END OF THE RUNWAY AND COLLIDED WITH SEVERAL OTHER OBSTACLES PRIOR TO THE AIRPLANE COMING TO REST IN A FIELD. THE AIRPLANE OWNER WAS INTERVIEWED OVER THE TELEPHONE BY THE SAFETY BOARD INVESTIGATOR-IN-CHARGE ON DECEMBER 30, 2003. THE OWNER STATED THAT HE HAD PURCHASED THE AIRPLANE THAT DAY AND HAD BEEN PRESENT DURING THE PRE-BUY INSPECTION. THERE WERE NO DISCREPANCIES FOUND DURING THE INSPECTION. THE FUEL TANKS WERE FILLED TO CAPACITY AT THAT TIME. THE OWNER, WHO ONLY HAD A ROTORCRAFT RATING ON HIS PRIVATE PILOT CERTIFICATE, HAD HIRED THE PILOT TO FLY THE AIRPLANE FROM LAS VEGAS TO CHINO. FOLLOWING DEPARTURE FROM LAS VEGAS AND THE CLIMB TO ALTITUDE, THE PILOT AND THE OWNER NOTED THAT THE RIGHT WING FUEL GAGE WAS SHOWING A LOWER THAN EXPECTED LEVEL, AND, BY THE TIME THE FLIGHT HAD REACHED BAKER, CALIFORNIA, (ABOUT HALFWAY ON THE APPROXIMATELY 220-MILE FLIGHT) THE GAGE WAS INDICATING EMPTY. THE PILOT SWITCHED THE FUEL SELECTOR TO THE LEFT TANK AND CONTINUED ON TOWARD CHINO, ALTHOUGH BOTH OF THEM WERE SOMEWHAT ALARMED BY THE LEFT TANK AND CONTINUED ON TOWARD CHINO, ALTHOUGH BOTH OF THEM WERE SOMEWHAT ALARMED BY THE APPARENT HIGH FUEL CONSUMPTION. AS THE FLIGHT NEARED RIALTO, THE LEFT FUEL GAGE WAS READING A VERY LOW QUANTITY AND THE PILOT THEN DECLARED THE EMERGENCY. THE PILOT SPIRALED DOWN OVER THE AIRPORT, BUT WAS TOO HIGH AND FAST FOR A LANDING ON RUNWAY 24, AND HE BEGAN A GO-AROUND. THE ENGINE LOST POWER JUST AFTER THE PILOT MOVED THE THROTTLE FORWARD AND THE AIRPLANE CRASHED INTO THE FENCE AND WENT OUT INTO THE FIELD. FAA INSPECTORS FROM THE RIVERSIDE, CALIFORNIA, FLIGHT STANDARDS DISTRICT OFFICE EXAMINED THE AIRPLANE ON DECEMBER 31. THEY REPORTED THAT THERE WAS NO FUEL STAINING EVIDENT ON THE EXTERIOR OF THE AIRPLANE. ABOUT 10.5 GALLONS OF FUEL WERE DRAINED FROM THE RIGHT TANK AND APPROXIMATELY 3 GALLONS WERE RECOVERED FROM THE LEFT TANK. THE FUEL TANK VENT SYSTEM, INCLUDING THE VENTED CAPS, WERE UNOBSTRUCTED; THE ANTI-SIPHON CHECK VALVE IN THE CAP VENTS WERE NORMAL. A FUEL LINE FITTING AT ONE INJECTOR NOZZLE WAS DISCONNECTED AND THE ELECTRIC FUEL PUMP WAS THEN ENERGIZED AT HIGH SETTING AND A CONTINUOUS STREAM OF FUEL POURED FROM THE DISCONNECTED LINE. THE FUEL LINES WERE INTACT FROM THE TANKS TO THE ENGINE, WITH NO EVIDENCE OF LEAKAGE AT ANY FITTING, INCLUDING THE FITTINGS DOWNSTREAM OF THE ELECTRIC PUMP. THE FUEL SYSTEM IS COMPRISED OF A FUEL TANK IN EACH WING. THE TOTAL SYSTEM CAPACITY IS 65 GALLONS, WITH 5 GALLONS (2.5 FOR EACH TANK) UNUSABLE. THE FUEL SELECTOR HAS THREE POSITIONS, OFF, LEFT, AND RIGHT. AN OPERATIONAL TEST OF THE ENGINE IS PLANNED IN A TEST CELL. ## 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 LAX04LA083](https://openairdocs.org/ntsb/LAX04LA083), Dec 30, 2003: Cessna 210 (N6539X), Rialto, CA, substantial damage. Probable cause: The pilot's inadequate in-flight planning/decision by his fuel mismanagement and his delay in initiating remedial action which resulted in fuel exhaustion and the loss of engine power. 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.