Flight profile · JetBlue

B6761

Boston (BOS) to San Juan (SJU) · scheduled 1:40 PM – 5:44 PM

FlyerIntel does not track flights in the air. This page describes how B6761 has historically performed, which is a different and more useful question when you are deciding what to book. For today’s status, check with JetBlue.

How B6761 performs

137 operations, 2025-04-30 to 2026-06-30.

On-time arrivals
76.1%
102 of 134 completed
Cancellation rate
2.19%
3 cancelled
Median arrival delay
-2 min
Average 9.9 min
Severe delays
9.7%
Arrived 60+ minutes late
Delay when late
65 min
Average, when 15+ min late
Departure punctuality
73.9%
Left the gate on time

B6761 arrived on time 76.1% of the time, against 67.8% for all BOSSJU flights — this specific departure is 8.3 percentage points better than the route as a whole. Against JetBlue’s own flights on this route it is 8.2 points better.

Source: US DOT Bureau of Transportation Statistics · 137 operations between 2025-04-30 to 2026-06-30

Against the rest of the route

On timeCancelledMedian delaySevereFlights
B676176.1%2.19%-2 min9.7%137
JetBlue on BOSSJU67.9%1.33%0 min12.5%3,770
All BOSSJU flights67.8%1.60%0 min12.2%5,869

Source: FlyerIntel analysis of US DOT BTS data · 2025-04-30 to 2026-06-30

Other routes B6761 has flown

A flight number is a slot in a schedule, and carriers reassign it. These are the other city pairs this number served in the analysis period.

RouteOperatedFlightsOn time
LGAPBI New York to West Palm Beach2023-07-012026-05-1860961.4%

Because the same number has served different journeys, the statistics above describe only the route B6761 currently operates. Blending them would produce an average of two different flights.

Data and methodology

Calculated by FlyerIntel from 137 records of B6761 operating BOSSJU, published by the US DOT Bureau of Transportation Statistics. A flight counts as delayed when it arrives 15 or more minutes after schedule. Cancelled and diverted flights are excluded from the on-time rate and reported separately. Flight numbers are resolved as carrier plus number plus route, because the same number serves different routes over time.

Full methodology · Report a problem