VOI3651
Flight history and live tracking for VOI3651, operated by Volaris. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Next flight
| Date | Sun 23 Aug 2026 |
| Route | MMPS PUERTO ESCONDIDO → MMTJ GENERAL ABELARDO L RODRIGUEZ INTERNATIONAL |
| Scheduled departure | 14:45 CST |
Scheduled and estimated times from the FAA SWIM feed, local to each airport.
Route
| Airline | Volaris |
| Observed route | MMPE → MMTJ |
Flight history 45 flights since Jun 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-20estimated | ? | ? | 21:01Z | 23:58Z | 2h 56m | D0D27 |
| 2026-08-19partial | MMTJ | ? | 17:00 PDT | D12C6 | ||
| 2026-08-18estimated | ? | ? | 21:45Z | 23:58Z | 2h 12m | D12C6 |
| 2026-08-17partial | MMTJ | ? | 17:40 PDT | N541VL | ||
| 2026-08-16estimated | ? | ? | 21:27Z | 21:52Z | 0h 24m | N541VL |
| 2026-08-14partial | MMTJ | ? | 20:49 PDT | D0984 | ||
| 2026-08-12partial | MMTJ | ? | 17:12 PDT | N526VL | ||
| 2026-08-11estimated | ? | ? | 21:16Z | 23:56Z | 2h 39m | N526VL |
Earlier flights (37) - back to 2026-06-11
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-23estimated | ? | ? | 21:18Z | 21:42Z | 0h 23m | N538VL |
| 2026-07-22estimated | ? | ? | 00:10Z | 00:34Z | 0h 24m | D0FF8 |
| 2026-07-21estimated | ? | ? | 21:23Z | 23:52Z | 2h 28m | D0FF8 |
| 2026-07-20partial | MMTJ | ? | 17:00 PDT | D0D41 | ||
| 2026-07-19estimated | ? | ? | 21:24Z | 23:58Z | 2h 33m | D0D41 |
| 2026-07-17partial | MMTJ | ? | 18:21 PDT | D0D40 | ||
| 2026-07-16estimated | ? | ? | 23:07Z | 23:32Z | 0h 24m | D0D40 |
| 2026-07-15partial | MMTJ | ? | 17:04 PDT | D10EC | ||
| 2026-07-14estimated | ? | ? | 21:15Z | 23:50Z | 2h 34m | D10EC |
| 2026-07-13partial | MMTJ | ? | 17:00 PDT | N509VL | ||
| 2026-07-12estimated | ? | ? | 21:30Z | 23:58Z | 2h 27m | N509VL |
| 2026-07-10estimated | MMSF | MMTJ | 17:09 PDT | 17:38 PDT | 0h 28m | D0CFD |
| 2026-07-09estimated | ? | ? | 21:20Z | 23:54Z | 2h 34m | D0CFD |
| 2026-07-08partial | MMTJ | ? | 17:02 PDT | N509VL | ||
| 2026-07-07estimated | ? | MMSF | 21:09Z | 16:59 PDT | 2h 49m | N509VL |
| 2026-07-06estimated | MMPE | MMTJ | 17:06 MST | 17:36 PDT | 0h 29m | D0867 |
| 2026-07-05estimated | ? | ? | 21:12Z | 23:54Z | 2h 41m | D0867 |
| 2026-07-03partial | MMTJ | ? | 17:00 PDT | D0984 | ||
| 2026-07-02estimated | MMAA | MMSF | 15:01 CST | 16:58 PDT | 2h 56m | D0984 |
| 2026-07-01partial | MMTJ | ? | 17:01 PDT | D1154 | ||
| 2026-06-30estimated | ? | ? | 21:51Z | 23:56Z | 2h 05m | D1154 |
| 2026-06-29estimated | MMPE | MMTJ | 17:09 MST | 17:42 PDT | 0h 33m | D0D8D |
| 2026-06-28estimated | ? | ? | 21:17Z | 23:54Z | 2h 36m | D0D8D |
| 2026-06-26partial | MMTJ | ? | 17:00 PDT | D10EC | ||
| 2026-06-25estimated | ? | ? | 21:05Z | 23:59Z | 2h 53m | D10EC |
| 2026-06-24partial | MMTJ | ? | 17:00 PDT | D0B35 | ||
| 2026-06-23estimated | ? | MMML | 20:58Z | 16:58 PDT | 2h 59m | D0B35 |
| 2026-06-22estimated | MMPE | MMTJ | 17:00 MST | 17:30 PDT | 0h 30m | N533VL |
| 2026-06-21estimated | ? | MMPE | 21:08Z | 16:58 MST | 2h 50m | N533VL |
| 2026-06-19partial | MMTJ | ? | 17:00 PDT | N508VL | ||
| 2026-06-18estimated | MMAA | MMSF | 15:06 CST | 16:58 PDT | 2h 51m | N508VL |
| 2026-06-17partial | MMTJ | ? | 17:00 PDT | D0E16 | ||
| 2026-06-16estimated | ? | ? | 21:00Z | 23:58Z | 2h 57m | D0E16 |
| 2026-06-15partial | MMTJ | ? | 17:10 PDT | D0B91 | ||
| 2026-06-14estimated | ? | ? | 21:11Z | 23:52Z | 2h 41m | D0B91 |
| 2026-06-12partial | MMTJ | ? | 17:00 PDT | D07F6 | ||
| 2026-06-11estimated | ? | MMPE | 23:25Z | 16:59 MST | 0h 33m | D07F6 |
Times are local to each airport. Hover for UTC. Flights marked estimated were completed with route prediction or partial coverage; partial records have a confirmed departure but no reliable arrival fix.
Get an email when VOI3651 flies + if it runs late.
Data access
Live positions and 365-day history for this flight are available through the PlaneTrack API (commercial use from $29/month) and as one-off CSV extracts from our own receiver network archive. Questions: [email protected]