Return to field — N657PP
KHIO · 022026-07-16 19:29 UTC· KHIO → KHIO· PETERSON HOLDING CO· LJ45
N657PP (Peterson Holding) had departed KHIO on 2026-07-16. SkyMeter detected a return to field at Portland Hillsboro Airport (KHIO) on runway 02 at 19:29 UTC. Peak cruise altitude FL425, turnaround area near Benton County, US. Approach stability score: 64/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4040 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Portland, OR, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4041 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
PORTLAND, OR, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/8071 2026-07-08 16:07Z – 2026-07-21 06:59Z SFC–400 ft
PORTLAND, OR
View FAA NOTAM →
SkyMeter cross-referenced this flight against FAA-published TFRs that were active during its window and within its geographic bounding box. Overlap doesn't necessarily mean violation — the aircraft may have been outside the TFR’s precise polygon or flying under air-traffic-control coordination.
Pilot review data
- Runway 02
- 42555 ft AGL at event
- 545 kt ground speed
- 0 fpm vertical
- Approach stability 64/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KHIO 161553Z 00000KT 10SM CLR 15/11 A3011 RMK AO2 SLP194 T01500106
Flight context
- N657PP
- Peterson Holding
- LJ45
- KHIO → KHIO
- 2026-07-16 19:29 UTC
- KHIO runway 02
All events on this flight
Automated analysis. Events shown on this page (such as go-around, unstable approach, or runway events) are heuristic classifications produced by algorithms from publicly broadcast ADS-B data. They are intended to surface flights of interest for further review — they are not findings of fact, and they do not determine pilot fault, regulatory compliance, or the cause of any occurrence. Coverage gaps and sensor noise can affect accuracy. Only the relevant civil aviation authority or accident investigation body can make official determinations. How we detect events · Dispute or correct this data