# Accident 19991222043139A: Gulstm 500, Georgetown, SC, December 22, 1999

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: December 22, 1999, 15:25 local time
- Place: Georgetown, SC
- Damage: Destroyed
- Phase of flight: To Init Climb(1st Pwr Reduct)
- Operating rules: General operating rules (Part 91)
- Location: 33.3609° N, 79.2897° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=33.3609&lon=-79.2897&mi=10
- Aircraft: N6261B, a cancelled registration (https://openairdocs.org/deregistered/N6261B-2013-08-20) (OpenAirDocs)
- Registry model: Aero Commander 500 (registry code 0141102, https://openairdocs.org/model/aero-commander-500) (OpenAirDocs)
- Registry engine: Lycoming 0-540 series (registry code 41532, https://openairdocs.org/engine/lycoming-0-540-series) (OpenAirDocs)
- Reported make and model: GULSTM 500
- Reported engine: LYC O540A2B
- People aboard: 2
- Fatal injuries: 2
- Pilot flight hours: 564 total, 69 in this make and model, 116 in the last 90 days
- NTSB investigation: [NTSB MIA00FA058](https://openairdocs.org/ntsb/MIA00FA058) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19991222043139A

## Narrative

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

(.4)THE NONINSTRUMENT-RATED PILOT ATTEMPTED VFR FLIGHT INTO KNOWN INSTRUMENT FLIGHT CONDITIONS AFTER BEING BRIEFED BY AN FAA AUTOMATED FLIGHT SERVICE STATION THAT VFR FLIGHT WAS NOT RECOMMENDED. THE PILOT ENCOUNTERED INSTRUMENT FLIGHT CONDITIONS WHILE MANEUVERING ON INITIAL TAKEOFF CLIMB, EXPERIENCED AN IN-FLIGHT LOSS OF CONTROL (STALL/SPIN) DUE TO FAILURE TO MAINTAIN AIRSPEED, AND SUBSEQUENT IN-FLIGHT COLLISION WITH TREES AND TERRAIN.          (-23) THE PILOT DEPARTED A NON-CONTROLLED AIRPORT IN IFR CONDITIONS AND IMPACTED THE GROUND APPROXIMATELY TWO MILES WEST OF THE AIRPORT.

## 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 MIA00FA058](https://openairdocs.org/ntsb/MIA00FA058), Dec 22, 1999: Aero Commander 500 (N6261B), Georgetown, SC, destroyed, 2 fatal. Probable cause: The noninstrument-rated pilot's improper decision to attempt VFR flight into known instrument flight conditions, willful disregard of FAA Automated Flight Service Station weather forecast/weather…

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.