# Incident 19980517018119I: Piper PA30, Tucson, AZ, May 17, 1998

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 17, 1998, 19:48 local time
- Place: Tucson, AZ
- Airport: Tucson International
- Damage: Minor damage
- Phase of flight: To Init Climb(1st Pwr Reduct)
- Operating rules: General operating rules (Part 91)
- Location: 32.1171° N, 110.9415° W: Placed by OpenAirDocs at TUCSON INTL (TUS), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=32.1171&lon=-110.9415&mi=10
- Aircraft: N373JT, a cancelled registration (https://openairdocs.org/deregistered/N373JT-2015-03-23) (OpenAirDocs)
- Registry model: Piper PA-30 (registry code 7103002, https://openairdocs.org/model/piper-pa-30) (OpenAirDocs)
- Registry engine: Lycoming IO-320 series (registry code 41509, https://openairdocs.org/engine/lycoming-io-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA30
- Reported engine: LYC IO320B1A
- People aboard: 2
- Fatal injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19980517018119I

## Narrative

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

SMOKE FROM NR1 COM ON CLIMBOUT. RETURNED. FOUND BURNT CAPACITOR.

## Other reports on N373JT (2)

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

- [Accident 20120302003679A](https://openairdocs.org/incident/20120302003679A), Mar 2, 2012: Piper PA-30 (N373JT), Roanoke, TX, Minor damage. 3/2/12: Responded to a call from the airport manager of 52F regarding an aircraft that had just landed gear up on the runway. Arrived on scene as iic at 15:15…
- [Incident 20020323003629I](https://openairdocs.org/incident/20020323003629I), Mar 23, 2002: Piper PA30 (N373JT), Tucson, AZ, Minor damage. (-23) On 23 March 2002 at approximately 1 p.m. local time I observed a Piper PA-30 twin comanche laying on its belly on runway 24. Tucson airport authority…

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.