Nonrev/JS IT update
11-20-2019, 08:58 AM
#1
Roll’n Thunder
Thread Starter
Joined APC: Oct 2009
Position: Pilot
Posts: 3,538
Nonrev/JS IT update
So I know recently there's been discussions on listing JS vs nonrev for commuting. I just encountered an apparently new update that sort of affects this. I had a JS booked on my first flight home after a trip, but a reroute led to an earlier release time that enabled me to run over and catch an earlier flight. I listed standby for this earlier flight, checked in, and had a seat assigned to me. When I scanned my boarding pass at the gate it gave a "double booking" error. The gate agent tried a couple of things but then I thought my JS booking on the next flight might be an issue so I went and canceled it and immediately afterwards by boarding pass scanned ok. (I had every intention of cancelling my JS before pushing, I had less than 20 minutes from block in to departure so I had to run right over and hadn't messed with it yet).
Anyways, it appears that the system will now see a JS reservation on a later flight as a double booking. I have no idea if the reverse is true (JS on first leg with a nonrev listing on second). Practically it shouldn't matter because if you have an assigned seat you should cancel the JS listing anways. Now it just forces you to do it prior to actaully boarding the plane.
Anyways, it appears that the system will now see a JS reservation on a later flight as a double booking. I have no idea if the reverse is true (JS on first leg with a nonrev listing on second). Practically it shouldn't matter because if you have an assigned seat you should cancel the JS listing anways. Now it just forces you to do it prior to actaully boarding the plane.
11-20-2019, 04:05 PM
#3
Gets Weekends Off
Joined APC: Feb 2015
Posts: 319
Originally Posted by tennisguru
So I know recently there's been discussions on listing JS vs nonrev for commuting. I just encountered an apparently new update that sort of affects this. I had a JS booked on my first flight home after a trip, but a reroute led to an earlier release time that enabled me to run over and catch an earlier flight. I listed standby for this earlier flight, checked in, and had a seat assigned to me. When I scanned my boarding pass at the gate it gave a "double booking" error. The gate agent tried a couple of things but then I thought my JS booking on the next flight might be an issue so I went and canceled it and immediately afterwards by boarding pass scanned ok. (I had every intention of cancelling my JS before pushing, I had less than 20 minutes from block in to departure so I had to run right over and hadn't messed with it yet).
Anyways, it appears that the system will now see a JS reservation on a later flight as a double booking. I have no idea if the reverse is true (JS on first leg with a nonrev listing on second). Practically it shouldn't matter because if you have an assigned seat you should cancel the JS listing anways. Now it just forces you to do it prior to actaully boarding the plane.
Anyways, it appears that the system will now see a JS reservation on a later flight as a double booking. I have no idea if the reverse is true (JS on first leg with a nonrev listing on second). Practically it shouldn't matter because if you have an assigned seat you should cancel the JS listing anways. Now it just forces you to do it prior to actaully boarding the plane.
Thread
Thread Starter
Forum
Replies
Last Post
