# Accident 20001021016241A: Amtr PITTSSPECS1S, Indiantown, FL, October 21, 2000 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: October 21, 2000, 10:30 local time - Place: Indiantown, FL - Airport: Indiantown Airport - Damage: Substantial damage - Collision: Midair collision, first aircraft - Phase of flight: Roll-Out (Fixed Wing) - Operating rules: General operating rules (Part 91) - Location: 27.0299° N, 80.4596° W: From the FAA, an estimate near the named town, within about 3 miles - Nearby events: https://openairdocs.org/map.md?lat=27.0299&lon=-80.4596&mi=10 - Aircraft: N56JP (not matched to a registry record) - Reported make and model: AMTR PITTSSPECS1S - Reported engine: LYC IO360B4A - People aboard: 1 - Fatal injuries: 0 - Pilot flight hours: 425 total, 67 in this make and model, 10 in the last 90 days - NTSB investigation: [NTSB MIA01LA010](https://openairdocs.org/ntsb/MIA01LA010) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20001021016241A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (-23) A/C ENTERED TRAFFIC LEFT DOWNWIND FOR RWY 13. WINDS WERE CROSSWIND TO RWY. PILOT CALLED UNICOM 123.0. PILOT STATED THERE WAS A LARGE AMOUNT OF RADIO TRAFFIC FROM NORTH COUNTY AIRPORT (F45) AND OKEELHOBEE COUNTY AIRPORT (OBE) ALSO USING 123.0 VHF. PILOT CALLED EACH LEG OF APPROACH AND LANDED LONG (APPROX 1500 FT) DOWN RWY 13. ON ROLL OUT A/C RIGHT WING STRUT AND UPPERWING TIP STRUCK OTHER A/C. EXITING RWY 31 AT GRASS TAXIWAY. PILOT SAID HE NEVER SAW OTHER A/C. NO INJURIES.. (.4) ON OCTOBER 21, 2000, ABOUT 1030 EASTERN DAYLIGHT TIME, A JIM PRICE PITTS SPECIAL S, N56JP, REGISTERED TO SEVERAL INDIVIDUALS, AND A BOEING A75N1 (PT17), N49713, REGISTERED TO AN INDIVIDUAL, COLLIDED DURING LANDING ROLLOUT AT INDIANTOWN AIRPORT, INDIANTOWN, FLORIDA, WHILE ON TITLE 14 CFR PART 91 PERSONAL FLIGHTS. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME AND NO FLIGHT PLANS WERE FILED FOR EITHER FLIGHT. BOTH AIRCRAFT RECEIVED SUBSTANTIAL DAMAGE AND THE COMMERCIAL-RATED PILOTS ON BOTH AIRCRAFT WERE NOT INJURED. N56JP DEPARTED FROM INDIANTOWN, THE SAME DAY, ABOUT 1000. N49173 DEPARTED FROM INDIANTOWN, THE SAME DAY, ABOUT 0930. THE PILOT OF N56JP STATED THAT AFTER DEPARTING FROM INDIANTOWN AIRPORT, HE FLEW AROUND THE LOCAL AREA. AFTER ABOUT 30 MINUTES, HE RETURNED TO INDIANTOWN AIRPORT FOR LANDING. THE WIND WAS FROM THE NORTHEAST AND HE ELECTED TO LAND ON RUNWAY 13. HE ANNOUNCED IS INTENTION ON THE UNICOM RADIO FREQUENCY, AND THERE WAS A LOT OF TRANSMISSIONS ON THE FREQUENCIES FROM PILOTS AT TWO OTHER LOCAL AIRPORTS. DURING LANDING ROLLOUT, AT ABOUT 30 MPH, HE SAW N49173, TO THE RIGHT AND IMMEDIATELY FORWARD. HE ATTEMPTED TO VEER LEFT AN COLLIDED WITH LOWER RIGHT WING OF N49173. BOTH AIRPLANES THEN TAXIED TO THE RAMP. THE PILOT OF N49713 STATED THAT AFTER DEPARTING FROM INDIANTOWN AIRPORT, HE FLEW AROUND THE LOCAL AREA. AFTER ABOUT 55 MINUTES, HE RETURN TO INDIANTOWN AIRPORT FOR LANDING. HE CALLED ON THE UNICOM FREQUENCY, REQUESTING TRAFFIC, BUT DID NOT GET A RESPONSE. HE CROSSED OVER THE AIRPORT AT 1,500 FEET AND OBSERVED FOR TRAFFIC. HE SAW NONE. THE WIND WAS OUT OF THE NORTHEAST, AND HE ELECTED TO LAND ON RUNWAY 31. HE MADE RADIO CALLS WHILE ENTERING THE PATTERN, DOWNWIND, BASE, AND ON FINAL APPROACH. AFTER LANDING, HE WAS TURNING OFF THE RUNWAY, AND WAS ABOUT 45 DEGREES TO THE RUNWAY, WHEN N56JP COLLIDED WITH THE LOWER RIGHT WING OF HIS AIRCRAFT. ## Other aircraft in the event - N49713, Boeing A75N1: [Accident 20001021016242A](https://openairdocs.org/incident/20001021016242A) ## 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 MIA01LA010](https://openairdocs.org/ntsb/MIA01LA010), Oct 21, 2000: Jim Price Pitts Special S (N56JP), Indiantown, FL, substantial damage. Probable cause: The failure of the pilot of N56JP, during landing rollout, to see and avoid N49713, who was turning off the runway after landing from the opposite direction, resulting in the 2 aircraft colliding on… 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.