How would you log a flight that diverts back to the departure airport?
Nov 29, 2019, 10:38 am
#1
Original Poster
Join Date: Feb 2018
Location: YYT
Programs: M-Bonvoy Platinum Elite, Aeroplan 50K, DragonPass, AMEX MR, NEXUS
Posts: 1,715
How would you log a flight that diverts back to the departure airport?
So for the first time ever today, I had a flight return to the departure airport due to a mechanical issue. I log all of my flights using the FR24 tool.
How would you guys log a flight like this (on FR24)? I am considering not logging it at all because it wasn't a "completed" flight segment.
How would you guys log a flight like this (on FR24)? I am considering not logging it at all because it wasn't a "completed" flight segment.
Nov 29, 2019, 11:01 am
#3
Original Poster
Join Date: Feb 2018
Location: YYT
Programs: M-Bonvoy Platinum Elite, Aeroplan 50K, DragonPass, AMEX MR, NEXUS
Posts: 1,715
Nov 29, 2019, 11:05 am
#4
FlyerTalk Evangelist
Join Date: Feb 2004
Location: YVR
Programs: AC SE 2MM; UA MP Premier Silver; Marriott Bonvoy LT Titanium Elite; Radisson; Avis PC
Posts: 35,255
@codfather scattered his posts across different threads... 
and seeing his response above, it seems that s/he actually didn't mention the flight in question, or I missed it.
Moving this here...
I made it as far as YQX without issue. Boarded the next flight to YYR, departed on-time, but turned around about 20 minutes in due to a mechanical issue (deicing problems on the BEH) and returned to YQX. They have since fixed the issue, but we are now delayed due to weather.
Oddly enough, the PAL airlines flight that just landed from YYT is continuing onto YYR without any "weather delays"...
I made it as far as YQX without issue. Boarded the next flight to YYR, departed on-time, but turned around about 20 minutes in due to a mechanical issue (deicing problems on the BEH) and returned to YQX. They have since fixed the issue, but we are now delayed due to weather.
Oddly enough, the PAL airlines flight that just landed from YYT is continuing onto YYR without any "weather delays"...
Nov 29, 2019, 11:21 am
#5
Original Poster
Join Date: Feb 2018
Location: YYT
Programs: M-Bonvoy Platinum Elite, Aeroplan 50K, DragonPass, AMEX MR, NEXUS
Posts: 1,715
@codfather scattered his posts across different threads...
and seeing his response above, it seems that s/he actually didn't mention the flight in question, or I missed it.
and seeing his response above, it seems that s/he actually didn't mention the flight in question, or I missed it.
And you are correct, I neglected to mention it. See my post above yours though for the number.
Nov 29, 2019, 8:37 pm
#9
Join Date: Nov 2004
Location: PDX
Programs: AA LT PLT (3.6+ MM), UA 1K LT Gold, Hilton LT Diamond, Bonvoy Gold.
Posts: 1,660
When I was training for the instrument rating, the correct FAA terminology for a flight that departs from and arrives back at the same airport was called round robin. I'd put it in the remarks section of the flight plan. So I'd log it as "round robin"....
https://discussions.flightaware.com/...ight-plan/5483
https://discussions.flightaware.com/...ight-plan/5483
Nov 29, 2019, 9:30 pm
#10
Join Date: Dec 2002
Posts: 8,000
The mileage won't be accurate, but the segment count and time will be correct.
If the flight returned because of weather or maintenance, I would call it a diversion.
Nov 29, 2019, 10:18 pm
#12
Moderator, Air Canada; FlyerTalk Evangelist
Join Date: Feb 2015
Location: YYC
Programs: AC SE MM, FB Plat, WS Plat, BA Silver, DL GM, Marriott Plat, Hilton Gold, Accor Silver
Posts: 16,742
@codfather, as long as it took off, I would log it. For instance, last year I was doing an IAH-YYC that had a bird strike on takeoff. We circled around IAH for a while and then landed after they decided they couldn't ascertain what damage had been done and needed to abort, then we had to burn off some fuel. A couple hours later, with new crew and a new plane, we took off again. So my FlightMemory has 2x UA1780 that day, one IAH-IAH and the other IAH-YYC.
But to each his own. I keep track of gate-to-gate times. I know some people prefer to track only time in the air. On the couple of flights I've had that have diverted for tech stops only, I have logged those just based on the original route, e.g. YYC-IAH that diverted to HOU, I didn't enter a YYC-HOU and a HOU-IAH, I just left it as YYC-IAH, because I feel like if no one is allowed to get on or off the plane, it's still the same flight. I'm sure plenty of people would feel that each takeoff and landing should be tracked separately. And so on and so forth.
For flights that return to the same airport (whether due to diversion or because they're sightseeing flights), I will typically use FlightAware to estimate the distance and then override the calculated 0 distance with that number. If it's a plane/helicopter that isn't tracked on FlightAware, I just take a rough estimate of time and and average speed and calculate something approximate.
Not sure why you feel the need to be so critical. This is something that a great many people are interested in. In addition to FlightRadar's service mentioned by the OP, there's FlightMemory (to which ~200,000 people have signed up), OpenFlights, BA97, and probably a few others out there allowing people to keep track of their flights.
But to each his own. I keep track of gate-to-gate times. I know some people prefer to track only time in the air. On the couple of flights I've had that have diverted for tech stops only, I have logged those just based on the original route, e.g. YYC-IAH that diverted to HOU, I didn't enter a YYC-HOU and a HOU-IAH, I just left it as YYC-IAH, because I feel like if no one is allowed to get on or off the plane, it's still the same flight. I'm sure plenty of people would feel that each takeoff and landing should be tracked separately. And so on and so forth.
Not sure why you feel the need to be so critical. This is something that a great many people are interested in. In addition to FlightRadar's service mentioned by the OP, there's FlightMemory (to which ~200,000 people have signed up), OpenFlights, BA97, and probably a few others out there allowing people to keep track of their flights.
Nov 30, 2019, 8:08 am
#13
Original Poster
Join Date: Feb 2018
Location: YYT
Programs: M-Bonvoy Platinum Elite, Aeroplan 50K, DragonPass, AMEX MR, NEXUS
Posts: 1,715
@codfather, as long as it took off, I would log it. For instance, last year I was doing an IAH-YYC that had a bird strike on takeoff. We circled around IAH for a while and then landed after they decided they couldn't ascertain what damage had been done and needed to abort, then we had to burn off some fuel. A couple hours later, with new crew and a new plane, we took off again. So my FlightMemory has 2x UA1780 that day, one IAH-IAH and the other IAH-YYC.
But to each his own. I keep track of gate-to-gate times. I know some people prefer to track only time in the air. On the couple of flights I've had that have diverted for tech stops only, I have logged those just based on the original route, e.g. YYC-IAH that diverted to HOU, I didn't enter a YYC-HOU and a HOU-IAH, I just left it as YYC-IAH, because I feel like if no one is allowed to get on or off the plane, it's still the same flight. I'm sure plenty of people would feel that each takeoff and landing should be tracked separately. And so on and so forth.
For flights that return to the same airport (whether due to diversion or because they're sightseeing flights), I will typically use FlightAware to estimate the distance and then override the calculated 0 distance with that number. If it's a plane/helicopter that isn't tracked on FlightAware, I just take a rough estimate of time and and average speed and calculate something approximate.
Not sure why you feel the need to be so critical. This is something that a great many people are interested in. In addition to FlightRadar's service mentioned by the OP, there's FlightMemory (to which ~200,000 people have signed up), OpenFlights, BA97, and probably a few others out there allowing people to keep track of their flights.
But to each his own. I keep track of gate-to-gate times. I know some people prefer to track only time in the air. On the couple of flights I've had that have diverted for tech stops only, I have logged those just based on the original route, e.g. YYC-IAH that diverted to HOU, I didn't enter a YYC-HOU and a HOU-IAH, I just left it as YYC-IAH, because I feel like if no one is allowed to get on or off the plane, it's still the same flight. I'm sure plenty of people would feel that each takeoff and landing should be tracked separately. And so on and so forth.
For flights that return to the same airport (whether due to diversion or because they're sightseeing flights), I will typically use FlightAware to estimate the distance and then override the calculated 0 distance with that number. If it's a plane/helicopter that isn't tracked on FlightAware, I just take a rough estimate of time and and average speed and calculate something approximate.
Not sure why you feel the need to be so critical. This is something that a great many people are interested in. In addition to FlightRadar's service mentioned by the OP, there's FlightMemory (to which ~200,000 people have signed up), OpenFlights, BA97, and probably a few others out there allowing people to keep track of their flights.
I'll have a look on FA to estimate the distance. Katamarino as Adam said, lots of enthusiasts like to log flights! Not sure why you feel the need to criticize people that do so.
Dec 1, 2019, 8:26 pm
#14
Join Date: Nov 2004
Location: PDX
Programs: AA LT PLT (3.6+ MM), UA 1K LT Gold, Hilton LT Diamond, Bonvoy Gold.
Posts: 1,660
Since I first mentioned Round Robin , I assume you were addressing me, but not sure since you didn't quote. Anyway, if you were addressing me you assumed wrong, FAA PPL IR. Look me up on the FAA airmans database under my name... . And yes, in the US it is not uncommon for Instrument training flights to put Round Robin in the comments section for a training flight departing and arriving the same airport with multiple approaches along the way. Really surprised you've never heard of the practice....