Departure (JL65 Flight Schedule)
San Diego, United StatesPDT 00:00:00 DAY
Arrival (JL65 Flight Schedule)
Tokyo, JapanJST 00:00:00 DAY
Flight Radar Checker 8J 65
Live Flight Tracker Map
Flight JL65 from San Diego to Tokyo is operated by Jetall. Scheduled time of departure from San Diego Intl is 13:35 PDT and scheduled time of arrival in Narita Intl is 16:45 JST. The duration of the flight is 11 hours 10 minutes.
3.9 out of 5 stars / 19 votes
History Flight Information for JL65 from Flight Scanner System
| Date | Flight | Departure Airport | Arrival Airport | Scheduled | Plane | Estimated | ||
|---|---|---|---|---|---|---|---|---|
| Departure | Arrival | Departure | Arrival | |||||
| Wed, 15 Jul | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:35 PDT | 16:45 JST | |||
| Tue, 14 Jul | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:35 PDT | 16:45 JST | JA866J (Boeing B789) | 14:26 PDT | 16:44 JST |
| Sun, 12 Jul | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:35 PDT | 16:45 JST | 13:54 PDT | 16:47 JST | |
| Fri, 10 Jul | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:35 PDT | 16:45 JST | JA863J (Boeing B789) | 13:57 PDT | 16:34 JST |
| Wed, 08 Jul | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:35 PDT | 16:45 JST | JA863J (Boeing B789) | 13:49 PDT | 16:42 JST |
| Tue, 07 Jul | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:35 PDT | 16:45 JST | JA865J (Boeing B789) | 13:50 PDT | 16:46 JST |
| Sun, 05 Jul | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:35 PDT | 16:45 JST | 13:49 PDT | 16:47 JST | |
| Fri, 03 Jul | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:35 PDT | 16:45 JST | JA865J (Boeing B789) | 13:48 PDT | 16:50 JST |
| Wed, 01 Jul | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:35 PDT | 16:45 JST | JA863J (Boeing B789) | 13:49 PDT | 16:53 JST |
| Sun, 28 Jun | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:00 PDT | 16:45 JST | 13:15 PDT | 16:25 JST | |
| Fri, 26 Jun | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:00 PDT | 16:45 JST | 14:06 PDT | 17:21 JST | |
| Wed, 24 Jun | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:00 PDT | 16:45 JST | 13:24 PDT | 16:36 JST | |
| Tue, 23 Jun | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:00 PDT | 16:45 JST | JA868J (Boeing B789) | 13:26 PDT | 16:19 JST |
| Sun, 21 Jun | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:00 PDT | 16:45 JST | JA868J (Boeing B789) | 13:50 PDT | 16:57 JST |
| Fri, 19 Jun | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:00 PDT | 16:45 JST | JA867J (Boeing B789) | 13:25 PDT | 16:09 JST |
| Wed, 17 Jun | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:00 PDT | 16:45 JST | JA865J (Boeing B789) | 14:06 PDT | 16:50 JST |
| Tue, 16 Jun | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:00 PDT | 16:45 JST | JA861J (Boeing B789) | 13:57 PDT | 16:34 JST |
| Sun, 14 Jun | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:00 PDT | 16:45 JST | JA863J (Boeing B789) | 13:20 PDT | 16:32 JST |
| Fri, 12 Jun | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:00 PDT | 16:45 JST | JA867J (Boeing B789) | 14:25 PDT | 17:07 JST |
| Wed, 10 Jun | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:00 PDT | 16:45 JST | JA862J (Boeing B789) | 13:23 PDT | 16:36 JST |
| Tue, 09 Jun | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:00 PDT | 16:45 JST | JA861J (Boeing B789) | 13:19 PDT | 16:53 JST |
| Sun, 07 Jun | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:00 PDT | 16:45 JST | JA866J (Boeing B789) | 13:19 PDT | 16:31 JST |
| Fri, 05 Jun | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:00 PDT | 16:45 JST | 13:45 PDT | 16:34 JST | |
| Wed, 03 Jun | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:00 PDT | 16:45 JST | JA867J (Boeing B789) | 16:00 PDT | 13:20 JST |
| Tue, 02 Jun | JL65 | San Diego Intl (SAN) | Narita Intl (NRT) | 13:00 PDT | 16:45 JST | JA864J (Boeing B789) | 14:26 PDT | 17:37 JST |
Disclaimer for JL65 Flight Radar Data
Flight JL65 from San Diego Intl to Narita Intl data is collected from different sources. The data is for informational purposes only and PlaneMapper is not responsible for the accuracy and reliability of flight JL65 data.
