# Accident 20090525018069A: Gulstm 500S, Daytona Beach, FL, May 25, 2009

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: May 25, 2009, 08:46 local time
- Place: Daytona Beach, FL
- Airport: Daytona Beach International
- Damage: Substantial damage
- Phase of flight: Landing
- Operating rules: General operating rules (Part 91)
- Location: 29.1847° N, 81.0464° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=29.1847&lon=-81.0464&mi=10
- Aircraft: N73U, a cancelled registration (https://openairdocs.org/deregistered/N73U-2009-08-11) (OpenAirDocs)
- Registry model: Aero Commander 500 S (registry code 0141107, https://openairdocs.org/model/aero-commander-500-s) (OpenAirDocs)
- Registry engine: Lycoming IO-720 series (registry code 41546, https://openairdocs.org/engine/lycoming-io-720-series) (OpenAirDocs)
- Reported make and model: GULSTM 500S
- Reported engine: LYC IO720B1BD
- People aboard: 1
- Fatal injuries: 1
- Other injuries: 0
- Pilot flight hours: 1,470 total, 574 in this make and model, 7 in the last 90 days
- NTSB investigation: [NTSB ERA09FA303](https://openairdocs.org/ntsb/ERA09FA303) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20090525018069A

## Narrative

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

(-23) THE AIRPLANE IMPACTED TERRAIN SHORT OF RUNWAY 25R DURING A FORCED LANDING AFTER TAKEOFF.  THE PILOT WAS SERIOUSLY INJURED, AND THE PILOT-RATED PASSENGER WAS FATALLY INJURED.  ATC DATA REVEALED THAT THE AIRPLANE DEPARTED FROM RUNWAY 7R.  ABOUT 1 MINUTE AFTER TAKEOFF, THE PILOT REPORTED "AN ENGINE FAILURE" AND ANNOUNCED HIS INTENTION TO RETURN FOR LANDING.  WITNESSES IN THE AIRPORT VICINITY REPORTED HEARING A "SURGING" ENGINE NOISE FROM THE AIRPLANE PASSED AS IT OVERHEAD.  POST-CRASH EXAMINATION OF THE AIRPLANE REVEALED THAT BOTH PROP CONTROLS WERE IN THE FULL-FORWARD POSITION AND THAT THE PROPS WERE NOT FEATHERED.  THE FLAPS WERE EXTENDED, AND THE LANDING GEAR WAS IN THE DOWN POSITION.  NO EVIDENCE OF MECHANICAL MALFUNCTION WAS FOUND.  ONLY TRACES QUANTITIES OF FUEL WERE FOUND IN THE AIRCRAFT FUEL SYSTEM.  THE MECHANIC WHO MAINTAINED THE AIRPLANE REPORTED THAT THE PILOT HAD REPORTED PROBLEMS WITH THE ACCURACY OF THE FUEL QUANTITY INDICATORY SYSTEM A FEW MONTHS EARLIER.  THE FUEL GAUGE WAS REPLACED IN FEBRUARY 2009 BUT THAT DID NOT RESOLVE THE PROBLEM.  THE MECHANIC ADVISED THE PILOT TO BRING THE AIRPLANE IN FOR DEFUELING AND DIAGNOSIS OF THE TRANSMITTER, BUT THE PILOT HAD NOT DONE SO AS THE DATE OF THE ACCIDENT.

## 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 ERA09FA303](https://openairdocs.org/ntsb/ERA09FA303), May 25, 2009: Aero Commander 500 S (N73U), Daytona Beach, FL, substantial damage, 1 fatal. Probable cause: A total loss of engine power due to fuel exhaustion as a result of the pilot’s inadequate preflight inspection.

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.