# Accident 20000911016289A: Piper PA28161, Fort Pierce, FL, September 11, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 11, 2000, 12:47 local time
- Place: Fort Pierce, FL
- Airport: St Lucie County International
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 27.4995° N, 80.3590° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=27.4995&lon=-80.3590&mi=10
- Aircraft: N9208N, a cancelled registration (https://openairdocs.org/deregistered/N9208N-2001-03-07) (OpenAirDocs)
- Registry model: Piper PA-28-161 (registry code 7102803, https://openairdocs.org/model/piper-pa-28-161) (OpenAirDocs)
- Reported make and model: PIPER PA28161
- People aboard: 1
- Fatal injuries: 1
- NTSB investigation: [NTSB ATL00FA091](https://openairdocs.org/ntsb/ATL00FA091) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000911016289A

## Narrative

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

(-23) N9208N WAS ON FINAL FOR RUNWAY 9 AT ST LUCIE COUNTY INTERNATIONAL AIRPORT, FORT PIERCE, FL (FPR) FOR A REQUESTED TOUCH AND GO. N54235 WAS ON A STRAIGHT IN APPROACH FROM THE WEST FOR THE SAME RUNWAY. A/C COLLIDED IN FLIGHT AT APPROXIMATELY 2 MILES FROM THE APPROACH END OF RUNWAY 9. BOTH A/C WERE IN COMMUNICATION WITH THE FPR CONTROL TOWER.

## 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 ATL00FA091](https://openairdocs.org/ntsb/ATL00FA091), Sep 11, 2000: Piper PA-28-161 (N9208N), Ft. Pierce, FL, destroyed, 2 fatal. Probable cause: Failure of local controller to provide adequate spacing between two airplanes that resulted in a midair collision. Contributing Factors: the local controller declined receiving a formal brief before…

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.