Unstable approach — POE486

POE486 (Porter Airlines (Canada)) was operating from CYYC to CYHM on 2026-08-01. SkyMeter detected a low approach-stability score at John C. Munro Hamilton International Airport (CYHM) on runway 24 at 03:50 UTC. Trace data at the event: 1903 ft AGL, 167 kt GS. Approach stability score: 45/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 2 kt wind, 2 kt crosswind component, 16,093 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.

• SECURITY6/4348 2026-03-08 07:00Z – 2026-11-01 06:59Z SFC–2,400 ft

  GRAND FORKS AFB, ND, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• HAZARDS6/6777 2026-07-19 19:05Z – 2026-08-20 07:00Z SFC–7,000 ft

  10NM N ELY, MN, Sunday, July 19, 2026 through Thursday, August 20, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6779 2026-07-19 19:09Z – 2026-08-20 07:00Z SFC–7,000 ft

  20NM N ELY, MN, Sunday, July 19, 2026 through Thursday, August 20, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6899 2026-07-20 14:30Z – 2026-08-02 06:00Z SFC–7,000 ft

  14NM N ORR, MN, Monday, July 20, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7199 2026-07-21 14:00Z – 2026-08-03 02:00Z SFC–7,000 ft

  20NM N ELY, MN, Tuesday, July 21, 2026 through Monday, August 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8871 2026-07-27 14:00Z – 2026-08-09 04:00Z SFC–8,000 ft

  83NM N SPEARFISH, SD, Monday, July 27, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8883 2026-07-27 14:00Z – 2026-08-09 04:00Z SFC–11,000 ft

  23NM SE HAMILTON, MT, Monday, July 27, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9566 2026-07-28 17:15Z – 2026-08-11 04:00Z SFC–10,000 ft

  33NM SW PHILIP, SD, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9803 2026-07-28 21:15Z – 2026-08-01 23:45Z SFC–200 ft

  0.5NM NE MENASHA, WI, Tuesday, July 28, 2026 through Saturday, August 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9880 2026-07-29 14:00Z – 2026-08-12 03:00Z SFC–9,000 ft

  26NM E MILES CITY, MT, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0287 2026-07-30 13:00Z – 2026-08-01 05:00Z SFC–2,500 ft

  21NM NW ELY, MN, Thursday, July 30, 2026 through Saturday, August 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0307 2026-07-30 14:00Z – 2026-08-13 04:00Z SFC–12,000 ft

  20NM SE HELENA, MT, Thursday, July 30, 2026 through Thursday, August 13, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/8432 2026-07-31 16:30Z – 2026-08-02 20:30Z SFC–16,000 ft

  St Cloud, MN, Friday, July 31, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0709 2026-07-31 22:58Z – 2026-08-02 04:00Z SFC–12,000 ft

  56NM E HELENA, MT, Friday, July 31, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0711 2026-08-01 01:16Z – 2026-08-02 04:00Z SFC–8,000 ft

  23NM S BILLINGS, MT, Saturday, August 1, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0716 2026-08-01 02:45Z – 2026-08-02 12:00Z SFC–9,500 ft

  17NM NE IDAHO FALLS, ID, Saturday, August 1, 2026 through Sunday, August 2, 2026 UTC

  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.

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