Unstable approach — ROS

YPJT · 06L

2026-04-01 01:25 UTC· JFC DARWIN PTY LTD· C402

ROS (JFC Darwin Pty) was inbound to YPJT on 2026-04-01. SkyMeter detected a low approach-stability score at Perth Jandakot Airport (YPJT) on runway 06L at 01:25 UTC. Trace data at the event: 683 ft AGL, 110 kt GS. Approach stability score: 39/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 4 kt wind, 3 kt crosswind component, 9,994 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.

Pilot review data

  • Runway 06L
  • 683 ft AGL at event
  • 110 kt ground speed
  • 0 fpm vertical
  • Approach stability 39/100
  • 4 kt wind
  • 3 kt crosswind component
  • 9,994 m visibility
  • YPJT 151230Z AUTO 16003KT 9999 // NCD 12/08 Q1023

Flight context

  • ROS
  • JFC Darwin Pty
  • C402
  • 2026-04-01 01:25 UTC
  • YPJT runway 06L

All events on this flight

Unstable approach 01:25:35 UTC · YPJT runway 06L · 683 ft AGL · 110 kt GS
Unstable approach 01:25:35 UTC · YPJT runway 06L · 683 ft AGL · 110 kt GS
Unstable approach 01:25:35 UTC · YPJT runway 06L · 680 ft AGL · 110 kt GS
Unstable approach 01:25:35 UTC · YPJT runway 06L · 683 ft AGL · 110 kt GS

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

SkyMeter · trace data observed via ADS-B· YPJT