# Accident 20031019024889A: Piper PA32300, Everglades, FL, October 19, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 19, 2003, 14:00 local time
- Place: Everglades, FL
- Airport: Everglades Airport
- Damage: Damage unknown
- Phase of flight: Forced/Precautionary Landing
- Operating rules: General operating rules (Part 91)
- Location: 25.8486° N, 81.3900° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=25.8486&lon=-81.3900&mi=10
- Aircraft: N198GM, registered now (https://openairdocs.org/aircraft/N198GM) (OpenAirDocs)
- Registry model: Piper PA-32-300 (registry code 7103212, https://openairdocs.org/model/piper-pa-32-300) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA32300
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 17,000 total, 250 in this make and model, 30 in the last 90 days
- NTSB investigation: [NTSB MIA04CA006](https://openairdocs.org/ntsb/MIA04CA006) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20031019024889A

## Narrative

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

(-23) WHILE DEPARTING EVERGLADES CITY AIRPORT (XO1), SUNDAY, OCTOBER 19, 2003, UNICOM PERSONNEL NOTICED THAT THE FORWARD BAGGAGE DOOR WAS OPEN AND BAGGAGE WAS FALLING FROM THE COMPARTMENT WHILE IN FLIGHT. UNICOM PERSONNEL CONTACTED THE PILOT TO INFORM. PILOT REPLIED THAT HE WAS GOING TO RETURN FOR LANDING. RWY 33 WAS THE ACTIVE. AIRPORT PERSONNEL WHO WITNESSED THE APPROACH FOR LANDING STATED IT APPEARED N198GM LANDED SHORT OF THE RWY. UPON ARRIVING AT XO1 AND COMPLETING AN INVESTIGATION, THE DAMAGE TO THE PLANT LIFE AND GROUND APPROX. 40 FEET FROM THE APPROACH END OF RWY 33, WAS CONSISTENT WITH THE WITNESSES OBSERVATION OF THE AIRCRAFT LANDING SHORT. AFTER THE ACCIDENT THE PILOT OF THE N198GM STATED TO AIRPORT PERSONNEL THAT HE LANDED SHORT OF RWY 33. STATEMENTS FROM PILOT AND AIRPORT PERSONNEL CONFIRM RUNWAY WAS UNDERSHOT.

## 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 MIA04CA006](https://openairdocs.org/ntsb/MIA04CA006), Oct 19, 2003: Piper PA-32-300 (N198GM), Everglades City, FL, substantial damage. Probable cause: The pilot's failure to maintain the proper glide path during the approach to land, which resulted in him undershooting the runway.

## Other reports on N198GM (4)

Matched to the same aircraft by N-number and date.

- [Incident 19960201003019I](https://openairdocs.org/incident/19960201003019I), Feb 1, 1996: Piper PA32300 (N198GM), Placid, FL. Narrative: on February 1, 1996, the pilot of N198GM attempted a take-off in a PA-32-300, in instrument conditions, heavy fog, and limited visibility. The pilot…
- [Incident 19920206062189I](https://openairdocs.org/incident/19920206062189I), Feb 6, 1992: Piper PA32300 (N198GM), Ukiah, CA, Minor damage. Pilot taxied off end of taxiway into a shallow ditch. Taxiway not lighted.
- [Incident 19880930062849I](https://openairdocs.org/incident/19880930062849I), Sep 30, 1988: Piper PA32300 (N198GM), Carmel Valley, CA, Minor damage. Approach too high. Struck trees on go around when engine lost power. Fuel tank mismanagement may have caused loss.
- [Incident 19790731014319I](https://openairdocs.org/incident/19790731014319I), Jul 31, 1979: Piper PA32300 (N198GM), Fresno, CA. Aborted takeoff after engine failed. Found mag coupling failed.

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.