Flight
GAP2015
Flight history and live tracking for GAP2015, operated by Air Philippines. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Air Philippines |
| Observed route | RPUF → RPLL |
Flight history 49 flights since Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-16estimated | ? | ? | 03:12Z | 05:28Z | 2h 16m | RP-C8397 |
| 2026-08-15partial | RPLL | ? | 10:53 PST | RP-C8620 | ||
| 2026-08-14partial | RPLL | ? | 10:48 PST | RP-C8615 | ||
| 2026-08-12partial | RPLL | ? | 11:00 PST | RP-C8611 |
Earlier flights (45) - back to 2026-03-13
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-22estimated | ? | ? | 02:49Z | 04:30Z | 1h 41m | 7584E4 |
| 2026-07-19partial | RPLL | ? | 10:53 PST | RP-C8606 | ||
| 2026-07-18partial | RPLL | ? | 10:47 PST | RP-C8611 | ||
| 2026-07-12partial | RPLL | ? | 10:57 PST | RP-C8611 | ||
| 2026-07-11partial | RPLL | ? | 11:10 PST | RP-C8619 | ||
| 2026-07-10partial | RPLL | ? | 10:54 PST | 7584E4 | ||
| 2026-07-08partial | RPLL | ? | 11:04 PST | RP-C8620 | ||
| 2026-06-29partial | RPLL | ? | 10:51 PST | RP-C8604 | ||
| 2026-06-21estimated | RPUF | RPLL | 11:01 PST | 11:22 PST | 0h 20m | RP-C8611 |
| 2026-06-17estimated | RPUF | RPLL | 10:59 PST | 11:22 PST | 0h 22m | 7584D7 |
| 2026-06-15partial | RPLL | ? | 11:01 PST | RP-C8619 | ||
| 2026-06-12partial | RPLL | ? | 11:11 PST | RP-C8620 | ||
| 2026-05-29partial | RPLL | ? | 10:48 PST | 7584D7 | ||
| 2026-05-25partial | RPLL | ? | 11:39 PST | RP-C8397 | ||
| 2026-05-24estimated | RPUF | RPLL | 11:17 PST | 12:59 PST | 1h 41m | RP-C8397 |
| 2026-05-22partial | RPLL | ? | 11:03 PST | RP-C8619 | ||
| 2026-05-21partial | RPLL | ? | 10:41 PST | 7584D7 | ||
| 2026-05-19partial | RPLL | ? | 09:47 PST | RP-C8611 | ||
| 2026-05-12estimated | RPUZ | RPLL | 11:33 PST | 12:10 PST | 0h 36m | RP-C8397 |
| 2026-05-10estimated | RPUF | RPLL | 10:57 PST | 11:26 PST | 0h 29m | RP-C8611 |
| 2026-05-09estimated | RPUF | RPLL | 10:31 PST | 10:58 PST | 0h 26m | 7584D7 |
| 2026-05-07estimated | RPUF | RPLL | 10:52 PST | 12:59 PST | 2h 06m | RP-C8611 |
| 2026-05-03estimated | RPUF | RPLL | 11:14 PST | 11:44 PST | 0h 29m | RP-C8609 |
| 2026-05-02partial | RPLL | ? | 10:51 PST | RP-C8397 | ||
| 2026-05-01partial | RPLL | ? | 13:01 PST | RP-C8620 | ||
| 2026-04-30partial | RPLL | ? | 10:46 PST | RP-C8620 | ||
| 2026-04-29partial | RPLL | ? | 10:54 PST | RP-C8611 | ||
| 2026-04-27partial | RPLL | ? | 11:18 PST | 7584E4 | ||
| 2026-04-26partial | RPLL | ? | 10:46 PST | RP-C8609 | ||
| 2026-04-25partial | RPLL | ? | 10:53 PST | RP-C8609 | ||
| 2026-04-24partial | RPLL | ? | 10:46 PST | RP-C8611 | ||
| 2026-04-22partial | RPLL | ? | 10:44 PST | RP-C8393 | ||
| 2026-04-18partial | RPLL | ? | 11:22 PST | 7584D7 | ||
| 2026-04-15partial | RPLL | ? | 11:12 PST | RP-C8609 | ||
| 2026-04-14partial | RPLL | ? | 10:45 PST | RP-C8619 | ||
| 2026-04-12partial | RPLL | ? | 11:10 PST | 7584E4 | ||
| 2026-04-06partial | RPLL | ? | 10:45 PST | 7584E4 | ||
| 2026-04-05partial | RPLL | ? | 10:50 PST | RP-C8393 | ||
| 2026-04-03partial | RPLL | ? | 11:04 PST | RP-C8610 | ||
| 2026-04-02partial | RPLL | ? | 10:45 PST | 7584D7 | ||
| 2026-04-01partial | RPLL | ? | 10:52 PST | RP-C8606 | ||
| 2026-03-16partial | RPLL | ? | 10:26 PST | RP-C8610 | ||
| 2026-03-15partial | RPLL | ? | 10:36 PST | RP-C8610 | ||
| 2026-03-14partial | RPLL | ? | 11:01 PST | RP-C8606 | ||
| 2026-03-13partial | RPLL | ? | 10:56 PST | 7584D7 |
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.
Follow this flight
Get an email when GAP2015 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]