# Accident 20040501005819A: Amtr SKYBOLT, Philadelphia, MS, May 1, 2004

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: May 1, 2004, 11:00 local time
- Place: Philadelphia, MS
- Damage: Substantial damage
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 32.7667° N, 89.1000° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=32.7667&lon=-89.1000&mi=10
- Aircraft: N32DS, a cancelled registration (https://openairdocs.org/deregistered/N32DS-2017-06-07) (OpenAirDocs)
- Registry model: Sawyer SKYBOLT (registry code 05655E7, https://openairdocs.org/model/sawyer-skybolt) (OpenAirDocs)
- Registry engine: Lycoming O&VO-360 series (registry code 41514, https://openairdocs.org/engine/lycoming-o-vo-360-series) (OpenAirDocs)
- Reported make and model: AMTR SKYBOLT
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 6,000 total, 60 in this make and model, 9 in the last 90 days
- NTSB investigation: [NTSB ATL04CA108](https://openairdocs.org/ntsb/ATL04CA108) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20040501005819A

## Narrative

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

(-23) AIRCRAFT STRUCK A TOWER DURING CRUISE FLIGHT AT 1600' APPROX 11 MILES SOUTHEAST OF PHILIDELPHIA MS ON A 140 HEADING TO TOPTON AIRPORT IN MERIDIAN, MS FROM PHILIDELPHIA, MS.

## 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 ATL04CA108](https://openairdocs.org/ntsb/ATL04CA108), May 1, 2004: Sawyer Skybolt (N32DS), Philadelphia, MS, substantial damage. Probable cause: The pilot's failure to see and avoid a guy wire which resulted in an in-flight collision.

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.