Rejected takeoff — JRE715
KBJC · 032026-06-12 12:20 UTC· KBJC → KGTU· FLYEXCLUSIVE JET SHARE LLC· C25B
JRE715 (Flyexclusive JET Share) was operating from KBJC to KGTU on 2026-06-12. SkyMeter detected a rejectedtakeoff at Rocky Mountain Metropolitan Airport (KBJC) on runway 03 at 12:20 UTC. Trace data at the event: 5603 ft AGL, 75 kt GS. Approach stability score: 63/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 10 kt wind, 8 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)- SECURITY6/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft
SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local
View FAA NOTAM → - HAZARDS6/4313 2026-05-31 14:00Z – 2026-06-14 03:00Z SFC–8,000 ft
13NM NW CARLSBAD, NM, Sunday, May 31, 2026 through Sunday, June 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/7402 2026-06-10 20:57Z – 2026-06-23 04:00Z SFC–8,500 ft
34NM NE TRINIDAD, CO, Wednesday, June 10, 2026 through Tuesday, June 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/7481 2026-06-11 14:00Z – 2026-06-24 03:00Z SFC–8,500 ft
34NM NE TRINIDAD, CO, Thursday, June 11, 2026 through Wednesday, June 24, 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 03
- 5603 ft AGL at event
- 75 kt ground speed
- 0 fpm vertical
- Approach stability 63/100
- 10 kt wind
- 8 kt crosswind component
- 16,093 m visibility
- METAR KBJC 261558Z 18007KT 10SM CLR 24/05 A3014
Flight context
- JRE715
- Flyexclusive JET Share
- C25B
- KBJC → KGTU
- 2026-06-12 12:20 UTC
- KBJC runway 03
All events on this flight
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