# Accident 20030530010779A: Piper PA44180, Livermore, CA, May 30, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: May 30, 2003, 11:05 local time
- Place: Livermore, CA
- Damage: Substantial damage
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 37.6933° N, 121.8203° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=37.6933&lon=-121.8203&mi=10
- Aircraft: N3060K, a cancelled registration (https://openairdocs.org/deregistered/N3060K-2022-01-08) (OpenAirDocs)
- Registry model: Piper PA-44-180 (registry code 7104402, https://openairdocs.org/model/piper-pa-44-180) (OpenAirDocs)
- Registry engine: Lycoming O&VO-360 series (registry code 41514, https://openairdocs.org/engine/lycoming-o-vo-360-series) (OpenAirDocs)
- Reported make and model: PIPER PA44180
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 575 total, 425 in this make and model, 150 in the last 90 days
- NTSB investigation: [NTSB LAX03LA172](https://openairdocs.org/ntsb/LAX03LA172) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030530010779A

## Narrative

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

(-23) N3060K, A PA-44, DEPARTED LIVERMORE AIRPORT, LIVERMORE, CA ON AN IFR FLIGHT PLAN WITH A DESTINATION OF MATHER FIELD, SACRAMENTO, CA. THE INSTRUCTIONAL FLIGHT WAS CONDUCTED IN ACTUAL IMC CONDITIONS. THE AIRCRAFT WAS CLEARED THE LIVERMORE ONE (SID) WITH AN ASSIGNED ALTITUDE OF 4,000 FEET. THE CONTROLLER WORKING N3060K WAS ALSO WORKING A SECOND SECTOR. THE CONTROLLER ASSIGNED AN ALTITUDE OF 2,000 FEET TO A SECOND AIRCRAFT TO WHICH N3060K ACKNOWLEDGED. THE CONTROLLER DID NOT ACKNOWLEDGE N3060K'S READ BACK OF THE INCORRECT CLEARANCE. WHILE LEVEL AT 2,000 FEET N3060K STRUCK OBJECTS JUST ABOVE THE GROUND (TREES, PHONE LINE) BUT CONTINUED TO FLY. AFTER A CONTROLLABILITY CHECK, THE PILOT CONTINUED TO SACRAMENTO EXECUTIVE AIRPORT, SACRAMENTO, CA.

## 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 LAX03LA172](https://openairdocs.org/ntsb/LAX03LA172), May 30, 2003: Piper PA-44-180 (N3060K), Livermore, CA, substantial damage. Probable cause: the pilots acceptance of a clearance meant for another aircraft. Contributing to the accident was the failure of departure controller to detect the pilot's incorrect read back and the controllers…

## Other reports on N3060K (2)

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

- [Incident 20171005016319I](https://openairdocs.org/incident/20171005016319I), Oct 5, 2017: Piper PA-44-180 (N3060K), St. Petersburg, FL, No damage. Pilot reported flat tire to tower after it landed on run-way 36 at St. Petersburg airport, FL.
- [Incident 19890703036769I](https://openairdocs.org/incident/19890703036769I), Jul 3, 1989: Piper PA44180T (N3060K), Avalon, CA, Minor damage. Electrical problem en route. Did not check circuit breakers. Landed with gear up.

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.