# Accident 19990523021879A: Piper PA24, Portland, OR, May 23, 1999

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: May 23, 1999, 15:30 local time
- Place: Portland, OR
- Airport: Portland/Hillsboro Airport
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 45.5806° N, 122.9099° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=45.5806&lon=-122.9099&mi=10
- Aircraft: N6017P, a cancelled registration (https://openairdocs.org/deregistered/N6017P-2018-01-25) (OpenAirDocs)
- Registry model: Piper PA-24 (registry code 7102402, https://openairdocs.org/model/piper-pa-24) (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 PA24
- People aboard: 3
- Fatal injuries: 0
- NTSB investigation: [NTSB SEA99LA070](https://openairdocs.org/ntsb/SEA99LA070) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19990523021879A

## Narrative

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

(.19) ON MAY 23, 1999, APPROXIMATELY 1634 PACIFIC DAYLIGHT TIME, A PIPER PA-24, N6017P, SUSTAINED SUBSTANTIAL DAMAGE IN A LANDING WITH LESS THAN FULL GEAR EXTENSION AT HILLSBORO, OREGON. THERE WERE NO INJURIES TO THE AIRPLANE'S THREE OCCUPANTS, CONSISTING OF THE COMMERCIAL PILOT-IN-COMMAND, A FLIGHT INSTRUCTOR, AND A REAR-SEAT PASSENGER (WHO OWNED THE AIRPLANE.) THE FAA DID NOT REPORT ANY RECORD OF A FLIGHT PLAN BEING FILED FOR THE 14 CFR 91 INSTRUCTIONAL FLIGHT. THE FLIGHT WAS DESCRIBED AS A FLIGHT REVIEW/INSTRUMENT INSTRUCTIONAL FLIGHT. PRELIMINARY INFORMATION FURNISHED BY THE FAA INDICATED THAT THE AIRPLANE PERFORMED A 270 DEGREE TURN FOR TRAFFIC PRIOR TO ITS APPROACH, AND THAT THE AIRPLANE EXECUTED A GO-AROUND AFTER TOWER CONTROLLERS INFORMED THE PILOT THAT THE AIRPLANE'S LANDING GEAR DID NOT APPEAR TO BE DOWN. ON THE NEXT APPROACH, THE TOWER AGAIN INFORMED THE PILOT THAT THE AIRPLANE'S LANDING GEAR DID NOT APPEAR TO BE DOWN, BUT THE AIRPLANE CONTINUED TO LAND. THE AIRPLANE EITHER LANDED GEAR-UP (OR WITH PARTIAL GEAR EXTENSION) OR EXPERIENCED A GEAR COLLAPSE DURING LANDING. IN AN INITIAL INTERVIEW WITH AN FAA INSPECTOR, THE FLIGHT CREW REPORTED THAT THEY OBSERVED A             "DOWN-AND-LOCKED" LANDING GEAR INDICATION PRIOR TO THE OCCURRENCE. A NOSE LANDING GEAR ARM WAS NOTED TO BE BROKEN DURING POST-ACCIDENT EXAMINATION; HOWEVER, THE FAA INSPECTOR WHO EXAMINED THE AIRCRAFT AFTER THE ACCIDENT REPORTED TO THE NTSB THAT HE FOUND NO EVIDENCE OF PRE-EXISTING MALFUNCTIONS OR DAMAGE IN THE AIRPLANE'S ELECTRICALLY ACTUATED LANDING GEAR SYSTEM. (-23)THE PIC WAS CLEARED TO LAND #3 AT HILLSBORO AIRPORT. THE ALNDING GEAR WAS EXTENDED EARLY ON THE FINAL APPROACH. THE PILOT STATED SHE WAS OVERTAKING TRAFFIC AND EXECUTED A LEFT 270 DEGREE TURN, THE  CONTINUED THE FINAL APPROACH ON SHORT FINAL. THE PIC STATED THAT THE ELECTRICAL POWER SEEMED TO FAIL AND COMMUNICATION WITH THE TOWER WAS LOST. THE TOWER TWICE INSTRUCTED THE CREW TO GO AROUND BECAUSE THE LANDING GEAR DID NOT APPEAR TO BE PROPERLY EXTENDED. HOWEVER, THE PIC AND SIC STATED THEY DID NOT RECEIVE THIS INSTRUCTION AND CONTINUED THE APPROACH. ON LANDING THE GEAR COLLAPSED CAUSING SUBSTANTIAL DAMAGE.

## 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 SEA99LA070](https://openairdocs.org/ntsb/SEA99LA070), May 23, 1999: Piper PA-24-180 (N6017P), Hillsboro, OR, substantial damage. Probable cause: A loose alternator drive belt, and the flight crew's decision to continue flight with a known electrical system deficiency, resulting in disabling of the aircraft electrical system and landing with…

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.