Diversion — EJA976
KTTN · 062026-07-21 17:57 UTC· KVRB → KTTN· CHALKER INVESTMENTS INC, ECON O CHECK CORP, ELIJAH REED CORP, FE· C68A
EJA976 (Chalker Investments) was operating from KVRB to KMMU (Morristown Municipal Airport) on 2026-07-21. SkyMeter detected a diversion to Trenton Mercer Airport (KTTN) on runway 06 at 17:57 UTC. Peak cruise altitude FL435, turnaround area near Southport, US. METAR at the time reported 11 kt wind, 3 kt crosswind component, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/4931 2026-07-11 15:58Z – 2026-07-23 01:00Z SFC–3,000 ft
2NM NE SHALLOTTE, NC, Saturday, July 11, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/5843 2026-07-14 23:37Z – 2026-07-22 23:45Z SFC–4,200 ft
18NM SW WAYNESBORO, VA, Tuesday, July 14, 2026 through Wednesday, July 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/6848 2026-07-20 00:32Z – 2026-08-03 23:45Z SFC–3,000 ft
2NM W SHULERVILLE, SC, Monday, July 20, 2026 through Monday, August 3, 2026 UTC
View FAA NOTAM → - SECURITY6/6747 2026-07-20 12:30Z – 2026-07-24 06:00Z SFC–2,500 ft
MAYPORT, FL, Monday, July 20, 2026 through Friday, July 24, 2026 Local
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 06
- 192 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- 11 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KTTN 162153Z 21006KT 10SM CLR 27/17 A3027 RMK AO2 SLP243 T02720172
Flight context
- EJA976
- Chalker Investments
- C68A
- KVRB → KTTN
- 2026-07-21 17:57 UTC
- KTTN runway 06
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