Unstable approach — N504RP
KRDG · 182026-07-08 22:21 UTC· KOQU → KRDG· PTS AS LLC· G280
N504RP (PTS AS) was operating from KOQU to KRDG on 2026-07-08. SkyMeter detected a low approach-stability score at Reading Regional Carl A Spaatz Field (KRDG) on runway 18 at 22:21 UTC. Trace data at the event: 1449 ft AGL, 182 kt GS. Approach stability score: 34/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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft
NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY6/3955 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Smithfield, RI, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4115 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
BASKING RIDGE, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4117 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Warren, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3949 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Providence, RI, Monday, June 1, 2026 through Tuesday, July 21, 2026 Local
View FAA NOTAM → - SECURITY6/6851 2026-06-13 04:01Z – 2026-07-12 03:59Z SFC–1,000 ft
Harrison, NJ, Saturday, June 13, 2026 through Saturday, July 11, 2026 Local
View FAA NOTAM → - SECURITY6/7230 2026-06-13 04:01Z – 2026-07-20 03:59Z SFC–1,000 ft
New York, NY, Saturday, June 13, 2026 through Sunday, July 19, 2026 Local
View FAA NOTAM → - SECURITY6/9462 2026-06-24 04:00Z – 2026-07-21 03:29Z SFC–400 ft
Montclair, NJ, Wednesday, June 24, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/1081 2026-07-01 12:00Z – 2026-07-09 16:00Z SFC–2,000 ft
New York, NY, Wednesday, July 1, 2026 through Thursday, July 9, 2026 Local
View FAA NOTAM → - SECURITY6/1240 2026-07-01 12:00Z – 2026-07-09 16:00Z SFC–2,000 ft
New York, NY, Wednesday, July 1, 2026 through Thursday, July 9, 2026 Local
View FAA NOTAM → - SECURITY6/7980 2026-07-03 16:07Z – 2026-07-21 03:59Z SFC–400 ft
New Brunswick, NJ
View FAA NOTAM → - SECURITY6/7080 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft
Providence, RI
View FAA NOTAM → - SECURITY6/7081 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft
Smithfield, RI
View FAA NOTAM → - SECURITY6/7973 2026-07-07 16:07Z – 2026-07-21 03:59Z SFC–400 ft
Basking Ridge, NJ
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 18
- 1449 ft AGL at event
- 182 kt ground speed
- 0 fpm vertical
- Approach stability 34/100
- 2 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- KRDG 010954Z 00000KT 10SM CLR 17/16 A3007 RMK AO2 SLP185 T01720161 $
Flight context
- N504RP
- PTS AS
- G280
- KOQU → KRDG
- 2026-07-08 22:21 UTC
- KRDG runway 18
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