# Accident 20020529014839A: Beech F33A, Conway, SC, May 29, 2002 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: May 29, 2002, 17:38 local time - Place: Conway, SC - Damage: Destroyed - Operating rules: General operating rules (Part 91) - Location: 33.8803° N, 78.9250° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=33.8803&lon=-78.9250&mi=10 - Aircraft: N858KS, a cancelled registration (https://openairdocs.org/deregistered/N858KS-2003-09-08) (OpenAirDocs) - Registry model: Beech F33A (registry code 1151425, https://openairdocs.org/model/beech-f33a) (OpenAirDocs) - Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs) - Reported make and model: BEECH F33A - People aboard: 1 - Fatal injuries: 1 - NTSB investigation: [NTSB MIA02FA102](https://openairdocs.org/ntsb/MIA02FA102) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20020529014839A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (.19) ON MAY 29, 2002, ABOUT 1738 EASTERN DAYLIGHT TIME, A BEECH F33A, N858KS, REGISTERED TO A PRIVATE INDIVIDUAL, WAS LOST FROM RADIO AND RADAR CONTACT AND CRASHED IN A WOODED AREA NEAR CONWAY, SOUTH CAROLINA. INSTRUMENT METEOROLOGICAL CONDITIONS PREVAILED IN THE AREA AT THE TIME OF THE ACCIDENT AND AN INSTRUMENT FLIGHT RULES FLIGHT PLAN WAS FILED FOR THE 14 CFR PART 91 PERSONAL FLIGHT. THE AIRPLANE WAS DESTROYED BY IMPACT FORCES AND THE PRIVATE-RATED PILOT, THE SOLE OCCUPANT, WAS FATALLY INJURED. THE FLIGHT ORIGINATED ABOUT 1729, FROM THE GRAND STRAND AIRPORT, NORTH MYRTLE BEACH, SOUTH CAROLINA. REVIEW OF A CERTIFIED COPY OF THE VOICE TAPE FROM THE GRAND STRAND AIR TRAFFIC CONTROL TOWER (ATCT), REVEALED THAT THE PILOT RECEIVED IFR CLEARANCE AND WAS CLEARED TO TAXI TO RUNWAY 05. THE PILOT WAS ADVISED TO FLY RUNWAY HEADING AND WAS CLEARED FOR TAKEOFF. SHORTLY AFTER TAKEOFF, THE PILOT WAS ADVISED THE CONTACT MYRTLE BEACH APPROACH CONTROL ON FREQUENCY 119.2 BUT THE PILOT ATTEMPTED TO COMMUNICATE WITH MYRTLE BEACH APPROACH CONTROL ON THE GRAND STRAND ATCT FREQUENCY. THE PILOT WAS AGAIN ADVISED TO CONTACT MYRTLE BEACH APPROACH CONTROL AND DID ESTABLISH COMMUNICATIONS WITH THAT FACILITY. REVIEW OF A CERTIFIED COPY OF THE VOICE TAPE FROM MYRTLE BEACH APPROACH CONTROL REVEALED THAT THE AIRCRAFT WAS RADAR IDENTIFIED, THE FLIGHT WAS CLEARED TO CLIMB TO 4,000 FEET, AND THE CONTROLLER ASKED THE PILOT WHAT WAS HIS HEADING. THE PILOT REPLIED 330 DEGREES AND THAT HE WAS DEVIATING TO THE RIGHT AROUND A "...LITTLE BUILD-UP." THE CONTROLLER ASKED THE PILOT IF HE COULD FLY HEADING 360 DEGREES AND THE PILOT RESPONDED THAT HE WAS UNABLE. THE CONTROLLER ADVISED THE PILOT TO FLY HEADING 210 DEGREES FOR A VECTOR AROUND TRAFFIC WHICH THE PILOT ACKNOWLEDGED. THE CONTROLLER THEN ADVISED THE PILOT THAT WHEN LEAVING 2,600 FEET TO RESUME OWN NAVIGATION AND THAT DEVIATION APPROVED AS NECESSARY WHICH WAS ACKNOWLEDGED BY THE PILOT. THE CONTROLLER AGAIN ADVISED THE PILOT RESUME OWN NAVIGATION AND DEVIATION AS NECESSARY WHICH WAS ACKNOWLEDGED BY THE PILOT WHO STATED THAT HE WAS DEVIATING A LITTLE BIT TO THE SOUTH 2 TO 3 MILES THEN WILL PICK-UP MY NORTHWESTERLY HEADING. THERE WERE NO KNOWN WITNESSES TO THE ACCIDENT. AN INDIVIDUAL NEAR THE ACCIDENT SITE REPORTED THAT THE WEATHER CONDITIONS ABOUT THE TIME OF THE ACCIDENT INCLUDED HEAVY RAIN, THERE WAS NO REPORTED LIGHTNING. (-23) AIRCRAFT DEPARTED CRE AT 1738 HRS LOCAL TIME AND IMPACTED GROUND 12 MILES NE OF MYR ATCT. ## 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 MIA02FA102](https://openairdocs.org/ntsb/MIA02FA102), May 29, 2002: Beech F33A (N858KS), Conway, SC, destroyed, 1 fatal. Probable cause: The failure of the pilot to request in-flight weather avoidance assistance and his poor in-flight planning/decision for flying into a Level 5 thunderstorm resulting in an in-flight loss of control,… 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.