Unstable approach — N605JG
KTIW · 172026-07-12 17:27 UTC· KTIW → KTIW· SEHER ASSET MANAGEMENT LLC· B350
N605JG (Seher Asset Management) was operating from KTIW to KTIW on 2026-07-12. SkyMeter detected a low approach-stability score at Tacoma Narrows Airport (KTIW) on runway 17 at 17:27 UTC. Trace data at the event: 1358 ft AGL, 143 kt GS. METAR at the time reported 1 kt wind, 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/4011 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
BELLEVUE, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4013 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Seattle, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4033 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
RENTON, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4034 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Renton, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/3000 2026-07-05 20:27Z – 2026-07-13 05:00Z SFC–8,000 ft
3NM E WENATCHEE, WA, Sunday, July 5, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/3001 2026-07-05 20:31Z – 2026-07-13 05:00Z SFC–8,500 ft
8NM W CHELAN, WA, Sunday, July 5, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/3023 2026-07-06 15:00Z – 2026-07-13 05:00Z SFC–8,500 ft
8NM W CHELAN, WA, Monday, July 6, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/3024 2026-07-06 15:00Z – 2026-07-13 05:00Z SFC–8,000 ft
3NM E WENATCHEE, WA, Monday, July 6, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - SECURITY6/8078 2026-07-07 16:07Z – 2026-07-21 06:59Z SFC–400 ft
Airway Heights, WA
View FAA NOTAM → - SECURITY6/8079 2026-07-07 16:07Z – 2026-07-21 06:59Z SFC–400 ft
Spokane, WA
View FAA NOTAM → - AIR SHOWS/SPORTS6/3070 2026-07-10 20:00Z – 2026-07-12 23:59Z SFC–15,000 ft
Bremerton, WA, Friday, July 10, 2026 through Sunday, July 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/4954 2026-07-11 20:52Z – 2026-07-19 05:00Z SFC–8,500 ft
7NM S WENATCHEE, WA, Saturday, July 11, 2026 through Sunday, July 19, 2026 UTC
View FAA NOTAM → - SECURITY6/8073 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft
Renton, WA
View FAA NOTAM → - SECURITY6/8074 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft
Renton, WA
View FAA NOTAM → - SECURITY6/8080 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft
Seattle, WA
View FAA NOTAM → - SECURITY6/8081 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft
Bellevue, WA
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 17
- 1358 ft AGL at event
- 143 kt ground speed
- 0 fpm vertical
- 1 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- METAR KTIW 290753Z AUTO 19009G19KT 10SM SCT031 BKN038 OVC050 14/11 A2997 RMK AO2 RAE26 SLP146 P0000 T01390106
Flight context
- N605JG
- Seher Asset Management
- B350
- KTIW → KTIW
- 2026-07-12 17:27 UTC
- KTIW runway 17
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