# Accident 20150712009259A: Barron STARDUSTER SA-300, Whiteville, NC, July 12, 2015

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 12, 2015, 18:30 local time
- Place: Whiteville, NC
- Airport: Columbus County Municipal
- Damage: Destroyed
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 34.2744° N, 78.7131° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=34.2744&lon=-78.7131&mi=10
- Aircraft: N5618, a cancelled registration (https://openairdocs.org/deregistered/N5618-2016-08-09) (OpenAirDocs)
- Registry model: Barron STARDUSTER SA-300 (registry code 8660184, https://openairdocs.org/model/barron-starduster-sa-300) (OpenAirDocs)
- Registry engine: Continental IO-470-L (registry code 17348, https://openairdocs.org/engine/continental-io-470-l) (OpenAirDocs)
- Reported make and model: BARRON STARDUSTER SA-300
- Reported engine: CONT MOTOR IO-470-L
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 1,160 total, 15 in this make and model, 16 in the last 90 days
- NTSB investigation: [NTSB GAA15CA185](https://openairdocs.org/ntsb/GAA15CA185) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20150712009259A

## Narrative

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

PILOT INTENDED TO DO PRACTICE TOUCH AND GO MANEUVERS AND ON TOUCHDOWN, LOSS CONTROL AND VEERED OFF THE RUNWAY INTO A FIELD.

## 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 GAA15CA185](https://openairdocs.org/ntsb/GAA15CA185), Jul 12, 2015: Barron Starduster SA 300 (N5618), Whiteville, NC, substantial damage. Probable cause: The pilot's failure to maintain directional control during an attempted go-around, which resulted in a runway excursion and a collision with terrain.

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.