PGR1969 (390) was operating from KMFR to KBFL on 2026-07-12. SkyMeter detected a low approach-stability score at Meadows Field (KBFL) on runway 30R at 00:09 UTC. Trace data at the event: 1608 ft AGL, 136 kt GS. METAR at the time reported 10 kt wind, 1 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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft
BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local
View FAA NOTAM → - SECURITY6/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft
SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 2026 Local
View FAA NOTAM → - SECURITY6/4052 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4054 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4060 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Oakland, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4061 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
BERKLEY, CA, Monday, June 1, 2026 through Tuesday, July 21, 2026 Local
View FAA NOTAM → - SECURITY6/4204 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Santa Clara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7983 2026-07-05 14:07Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, CA
View FAA NOTAM → - SECURITY6/7984 2026-07-05 14:07Z – 2026-07-21 06:59Z SFC–400 ft
Oakland, CA
View FAA NOTAM → - SECURITY6/7985 2026-07-05 14:07Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, CA
View FAA NOTAM → - HAZARDS6/3807 2026-07-08 15:00Z – 2026-07-22 15:00Z SFC–9,000 ft
10NM SE FALL RIVER MILLS, CA, Wednesday, July 8, 2026 through Wednesday, July 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/4014 2026-07-08 16:17Z – 2026-07-22 15:00Z SFC–9,000 ft
10NM SE FALL RIVER MILLS, CA, Wednesday, July 8, 2026 through Wednesday, July 22, 2026 UTC
View FAA NOTAM → - SECURITY6/3031 2026-07-09 14:00Z – 2026-07-12 23:59Z SFC–400 ft
Stateline, NV, Thursday, July 9, 2026 through Sunday, July 12, 2026 Local
View FAA NOTAM → - HAZARDS6/4558 2026-07-10 04:00Z – 2026-07-21 15:00Z SFC–9,000 ft
10NM SE FALL RIVER MILLS, CA, Friday, July 10, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/4559 2026-07-10 04:00Z – 2026-07-21 15:00Z SFC–9,000 ft
10NM SE FALL RIVER MILLS, CA, Friday, July 10, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SPACE OPERATIONS6/3530 2026-07-11 15:00Z – 2026-07-12 06:00Z SFC–350 ft
30 ZLC AIRSPACE BLACK ROCK, NV, Saturday, July 11, 2026 through Sunday, July 12, 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.
Pilot review data
- Runway 30R
- 1608 ft AGL at event
- 136 kt ground speed
- 0 fpm vertical
- 10 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- METAR KBFL 291354Z 10004KT 10SM CLR 17/04 A2983 RMK AO2 SLP096 T01670044
Flight context
- PGR1969
- 390
- PRM1
- KMFR → KBFL
- 2026-07-12 00:09 UTC
- KBFL runway 30R
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