# Accident 20101110051009A: Piper PA-30, Tucson, AZ, November 10, 2010

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 10, 2010, 15:57 local time
- Place: Tucson, AZ
- Airport: Tucson International Airport
- Damage: Substantial damage
- Phase of flight: Ground/Ramp/Ma
- Operating rules: General operating rules (Part 91)
- Location: 32.1161° N, 110.9411° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=32.1161&lon=-110.9411&mi=10
- Aircraft: N628R, a cancelled registration (https://openairdocs.org/deregistered/N628R-2017-03-06) (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 PA-30
- Reported engine: LYCOMING IO-320 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport, flight instructor
- Pilot flight hours: 7,364 total, 1,169 in this make and model, 7 in the last 90 days
- NTSB investigation: [NTSB WPR11LA044](https://openairdocs.org/ntsb/WPR11LA044) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20101110051009A

## Narrative

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

11-10-10. INEFFECTIVE BRAKING  AFTER LANDING ON RUNWAY 11L AT TUCSON INTL AND LOST BRAKING AND DIRECTIONAL CONTROL AFTER EXITING AT INTERSECTION A13.  AIRCRAFT CROSSED ALPHA TAXIWAY AND THE RAMP, STRIKING THE FIRE DEPARTMENT BUILDING WITH THE AIRCRAFT'S RIGHT WING SECTION.  THIS CAUSED SUBSTANTIAL TO THE AIRCRAFT TIP TANK, WING AND RIGHT ENGINE PROPELLER.  NO INJURIES REPORTED.11-12-10.  ^PRIVACY DATA OMITTED^ CALLED THIS OFFICE FROM AN INTENSIVE CARE UNIT WHERE HE WAS RECOVERING FROM NEUROSURGERY.  HE STATED THAT HE SUFFERED A HEMATOMA AND THE SURGEON STATED IT APPEARED TO HAVE OCCURRED SEVERAL DAYS EARLIER.  ^PRIVACY DATA OMITTED^ WIFE STATED HE WAS LIMPING AFTER THE ACCIDENT WHERE HE RECEIVED NO INJURIES.  THIS COUPLED WITH ^PRIVACY DATA OMITTED^ HEADACHES OVER THE PAST WEEK  PROMPTED HER TO GET HIM TO A HOSPITAL FOR AN EXAMINATION, AT WHICH TIME HE WAS ADMITTED FOR SURGERY.  IT APPEARS THE LOSS OF CONTROL OF THE AIRCRAFT MAY HAVE BEEN DUE TO THIS MEDICAL AFFLICTION.^PRIVACY DATA OMITTED^ STATED HE WAS OPERATING ON A SPECIAL MEDICAL CERTIFICATE FOLLOWING A PREVIOUS CARDIOVASCULAR EVENT AND THAT HE WAS TAKING THE PRESCRIBED MEDICATION, COUMADIN.

## 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 WPR11LA044](https://openairdocs.org/ntsb/WPR11LA044), Nov 10, 2010: Piper PA30 (N628R), Tucson, AZ, substantial damage. Probable cause: The pilot's impairment by an undiagnosed medical condition, which resulted in a loss of directional control and subsequent collision with a building during the landing roll. Contributing to the…

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.