# Incident 20170406003439I: Cessna 441, Portland, OR, April 6, 2017

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: April 6, 2017, 15:57 local time
- Place: Portland, OR
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 45.5235° N, 122.6762° W: Placed by OpenAirDocs: center of Portland, OR, within about 7 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=45.5235&lon=-122.6762&mi=10
- Aircraft: N441BL, registered now (https://openairdocs.org/aircraft/N441BL) (OpenAirDocs)
- Registry model: Cessna 441 (registry code 2076020, https://openairdocs.org/model/cessna-441) (OpenAirDocs)
- Registry engine: Alliedsign TPE331-10N (registry code 02584, https://openairdocs.org/engine/alliedsign-tpe331-10n) (OpenAirDocs)
- Reported make and model: CESSNA 441
- Reported engine: ALLIEDSIGN TPE331 SERIES
- People aboard: 5
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot
- Pilot flight hours: 1,984 total
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20170406003439I

## Narrative

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

ON THURSDAY, APRIL 6, 2017, A CESSNA 441, REGISTERED AS N441BL, SERIAL NUMBER 4410237, WAS INVOLVED IN AN INCIDENT AT PORTLAND INTERNATIONAL AIRPORT (KPDX) IN WHICH THE AIRCRAFT SUFFERED MINOR DAMAGE.

THE FLIGHT ORIGINATED FROM CARSON AIRPORT (KCXP) IN CARSON CITY, NV AND BEGAN AN IFR CROSS COUNTRY FLIGHT TO KPDX, TO DROP OFF PASSENGERS.  THE AIRCRAFT'S FINAL DESTINATION WAS SKAGIT REGIONAL AIRPORT (KBVS) IN NORTHWESTERN PORTION OF WASHINGTON STATE .

THE PILOT IN COMMAND EXPLAINED THAT HE WAS CLEARED TO LAND ON RUNWAY 10L, AND HAD THREE GREEN LANDING GEAR LIGHTS INDICATING IT WAS IN THE DOWN POSITION.  THE PILOT ALSO STATED THAT HE COULD SEE THE NOSE GEAR EXTENDED THROUGH A REFLECTION OF THE AIRCRAFT?S PAINT.

HE EXPLAINED THAT IT WAS A NORMAL LANDING UP TO THE POINT OF THE NOSE GEAR TOUCHING DOWN ON THE RUNWAY.  AS THE NOSE GEAR TOUCHED DOWN, HE BEGAN TO HEAR GRINDING.    HE VERIFIED HIS FEET WERE NOT ON THE BRAKES, HOWEVER THE VIBRATIONS CONTINUED.  THE PILOT EXPLAINED THAT HE REVERSED THE PROPEPPELERS, CONTINUED TO DECELERATE, AND MENTIONED THAT HE STILL HAD SOME DIRECTIONAL CONTROL.  AT 60 KNOTS HE APPLIED THE BRAKES, MOVED THE PROPELLERS OUT OF REVERSE, AND BEGAN TO OBSERVE SPARKS.  THE PILOT STOPPED THE AIRCRAFT ON THE RUNWAY, SHUT IT DOWN, AND HAD EVERYONE EXIT THE AIRCRAFT.

AFTER EXITING THE AIRCRAFT, THE PILOT OBSERVED THE NOSE GEAR IN FLAMES.  AFTER THE EVENT, THE PILOT EXPLAINED THAT THE NOSE TIRE APPEARED TO HAVE SHREDDED AND SEPARATED FROM THE HUB.  THE WHEEL HUB APPEARED TO BE GROUND DOWN AS A RESULT OF CONTACT WITH THE SURFACE OF THE RUNWAY.  THE NOSE WHEEL TIRE GUARD WAS LATER LOCATED ON THE RUNWAY BY AIRPORT PERSONNEL.

THE PILOT STATED THAT HE PREPPARED THE AIRCRAFT AND PERFORMED A SATISFACTORY PREFLIGHT PRIOR TO HIS DEPARTURE FROM KCXP.  HE RECALLED THAT THERE WAS NO DISCREPENCIES WITH ANY OF THE TIRES WHEN HE VISUALLY CHECKED THEM.  THE PILOT EXPLAINED THAT HE BELIEVES THE TIRE COULD HAVE GONE FLAT IN FLIGHT.  HE EXPLAINED THAT HE COULD NOT ACCOUNT FOR ANY FOREIGN OBJECT DEBREES (FOD) THAT COULD HAVE OCCURRED DUIRNG ITS TAXI, TAKEOFF, OR DEPARTURE FROM KCXP.

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.
