I had a very interesting experience yesterday on a day trip to ROC from ISP. First it was interesting because the fare ISP-ROC-ISP was half of what it was LGA-ROC-LGA but that's another story.
The ISP-PHL encountered a ground stop at PHL ostensibly due to visibility (there must have been more than one cloud in the sky). We left about 1 hour late, and there were a good number of connections in jeopardy. I called Chairmans and they told me that the aircraft being used ISP-PHL was the same one going on to ROC so I should be okay no matter what.
As it turns out there was a minor mechanical delay on the PHL-ROC flight to fix a noise in the pressurization system. Overall we were delayed about 20 minutes.
When I returned to the airport to come home, I went to the club and inquired about making the 5:50 main line to PHL instead of the 7:55 Buzz Bucket. When my dear friend in the club tried to accommodate me she noticed my entire return reservation was cancelled. It appears that someone had protected me on the 1:20 PHL-ROC flight, and had me as a no show on that, even though I made the original flight. Of course due to her EXPERIENCE, the story had a happy ending as I was able to make the 5:50, where I met a great flight attendant who was aware of our organization, and then spent some time with my friends in the PHL clubs.
Here's my question to my good friends here--why would it be necessary to protect someone on a later flight IF the second leg is on the same aircraft? And even if it was done due to a possible mechanical, why would the system not automatically cancel a "protection" reservation when it noted I made the original flight. Is this a common glitch or did the person who made the protection do something wrong?
My sincere thanks and appreciation to all who fixed the problem--you guys are really the best!!! Had the problem occurred elsewhere (Term F) I would likely still be away from home!
Any comments would be greatly appreciated.
Thanks and my best to you all.........
The ISP-PHL encountered a ground stop at PHL ostensibly due to visibility (there must have been more than one cloud in the sky). We left about 1 hour late, and there were a good number of connections in jeopardy. I called Chairmans and they told me that the aircraft being used ISP-PHL was the same one going on to ROC so I should be okay no matter what.
As it turns out there was a minor mechanical delay on the PHL-ROC flight to fix a noise in the pressurization system. Overall we were delayed about 20 minutes.
When I returned to the airport to come home, I went to the club and inquired about making the 5:50 main line to PHL instead of the 7:55 Buzz Bucket. When my dear friend in the club tried to accommodate me she noticed my entire return reservation was cancelled. It appears that someone had protected me on the 1:20 PHL-ROC flight, and had me as a no show on that, even though I made the original flight. Of course due to her EXPERIENCE, the story had a happy ending as I was able to make the 5:50, where I met a great flight attendant who was aware of our organization, and then spent some time with my friends in the PHL clubs.
Here's my question to my good friends here--why would it be necessary to protect someone on a later flight IF the second leg is on the same aircraft? And even if it was done due to a possible mechanical, why would the system not automatically cancel a "protection" reservation when it noted I made the original flight. Is this a common glitch or did the person who made the protection do something wrong?
My sincere thanks and appreciation to all who fixed the problem--you guys are really the best!!! Had the problem occurred elsewhere (Term F) I would likely still be away from home!
Any comments would be greatly appreciated.
Thanks and my best to you all.........