# Incident 20260110000189I: Cessna P206D, Hillsboro, OR, January 10, 2026

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 10, 2026, 04:48 local time
- Place: Hillsboro, OR
- Airport: Portland-Hillsboro
- Damage: Minor damage
- Phase of flight: Taxi
- Operating rules: General operating rules (Part 91)
- Location: 45.5421° N, 122.9507° W: Placed by OpenAirDocs at PORTLAND-HILLSBORO (HIO), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=45.5421&lon=-122.9507&mi=10
- Aircraft: N206JD, registered now (https://openairdocs.org/aircraft/N206JD) (OpenAirDocs)
- Registry model: Cessna P206D (registry code 2073338, https://openairdocs.org/model/cessna-p206d) (OpenAirDocs)
- Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs)
- Reported make and model: CESSNA P206D
- Reported engine: CONT MOTOR IO 520 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 1,267 total, 94 in this make and model, 2 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20260110000189I

## Narrative

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

AS STATED BY THE PILOT:

THE PILOT CONTACTED HILLSBORO GROUND, LETTING THEM KNOW OF MY INTENTIONS TO DO A BRAKE BURN-IN, AND THAT THIS WOULD BE A GROUND OPERATION ONLY, AND WE WOULD EXIT THE RUNWAY TAXI BACK TO PARKING ON COMPLETION.  I REQUESTED ACCESS TO THE NON-ACTIVE RUNWAY BUT WAS DENIED, AND INFORMED I WOULD HAVE TO USE THE ACTIVE RUNWAY.

AFTER WAITING AT INTERSECTION BRAVO ON 31L, THE TOWER CLEARED ME FOR A FAST TAXI ON THE ACTIVE, BUT ASKED ME TO EXPEDITE AS THERE WAS TRAFFIC ON A LONG FINAL (AN MU-2). THE PILOT CONFIRMED WITH TOWER HIS INTENTION TO TAXI THE REMAINING LENGTH OF THE RUNWAY AND EXIT AT THE FAR END, BUT THAT THE PIPLOT WOULD DO HIS BEST TO EXPEDITE.

AFTER A FEW THOUSAND FEET OF THE BRAKE BURN-IN, BUT WELL SHORT OF THE END OF THE RUNWAY, THE TOWER ASKED THE PILOT TO EXIT THE RUNWAY.  AT THAT POINT THE BRAKES WERE TOO SOFT FROM INTENTIONAL OVERHEATING TO STOP THE AIRPLANE, SO I MISSED THE FIRST TAXIWAY.  A SECOND, URGENT CALL FROM THE TOWER TO EXIT IMMEDIATELY WAS RECEIVED, SO THE PILOT MADE A BEST EFFORT TO TURN OFF AT THE NEXT TAXIWAY, KILO.  THE BRAKES WERE STILL OVERHEATED AS THE PILOT HAD NOT YET BEGUN ANY SORT OF COOL DOWN PHASE, SO IT WAS DIFFICULT TO NEGOTIATE THIS TURN.  AS THE PILOT CAME AROUND, HE COULD SEE THAT I WAS GOING TO OVERSHOOT, SO HE SIMPLY AIMED BETWEEN TWO TAXI LIGHTS, ASSUMING THAT IT WOULD RESULT IN AN OVERRUN ONTO THE GRASS.  THE AIRCRAFT IS EQUIPPED WITH BIG TIRES FOR OFF-FIELD OPERATION.

THE PILOT DID NOT REALIZE WAS THAT ALL OF THE TURF IN THIS AREA WAS NEW, AND VERY SOFT.  AS THE PILOT ROLLED OFF OF THE TAXIWAY AT A FAIRLY LOW SPEED, THE NOSE GEAR SANK INTO THE SOFT GROUND, AS DID THE RIGHT MAIN TO A LESSER DEGREE, WITH THE AIRCRAFT COMING TO A COMPLETE STOP IN LESS THAN 10 SECONDS.

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.