Again, this isn't an RJ thread so you can hold the attitude, were all on the same team.

I know plenty, 2200TT is very competitive for a mil guy and we both know it's not the same as 2200TT on the civilian side. When I made the original posting I did make some assumptions. One, that the OP would be smart enough to network and start applying before getting out of the military. Obviously, getting a call from SWA isn't easy, but he's definitely competitive and you also ignored that I mentioned Spirit as well. It's also not easy to get on but he's even more competitive for them I would think. Granted I don't know exactly what he/she has been flying in the military either, I'm sure IP experience would go a long way as well. But Allegiant should definitely be the back-up plan to either of those places, not the first choice.

You like to attack people that don't love Allegiant. You say we're all telling falsehoods, please point out where? Nothing I've posted has been fabricated. You said yourself you haven't been TDY'd? That means there is a whole 'nother side to this company you haven't seen. The TDY situation has improved slighty, sure, but it's still a BIG issue here. The fact remains there are guys that have spent 6 of 9 months (or more) involuntary out of base. I could go on and on about the many other issues but that horse has been beat already.

And yes, truce, I have no desire to fight. I just call it as I see it.

 

2200 hours mil time isn't even up to their published mins. You have to have a at least 3000 to sign up for their job fair. And I agree, almost every other LCC would be a smarter choice right now compared to Allegiant, if you can get a call. 3000TT/1000PIC appears to be an unpublished min for mil guys, especially heavy guys. Fighter types 2200 is very competitive at all carriers. I have less than slightly less than that but job fairs and internal recs have gone farther. With SW internals aren't even looked at until after the interview. That means you have to have competitive quals to get to that point.

I was mostly responding to the OP about the lure of home every night. That is a huge draw. But like you said, there are strings attached to it and it's not a guarantee.

I wouldn't say anyone has outright lied, but stretched the truth and leaving out details and facts. For instance the PIE incident. Lots of details left out about what exactly happened. Even I don't know the full truth but I know more than what has been published here. I don't love Allegiant, but so far it's better than what I had, but a long ways to go.

 

In regards to the PIE incident.... doesn't ALG have a union, and isn't said union helping said crew defend themselves? If justified in firing, then the union should state that more to the story and move on, but if not, shouldn't the union be fighting the fight.... that's unity.

 

You see military is a two way street. If you're deemed to be a good addition to a compatriots company, many will go a mile to get you onboard.

If you've walked on a lot of backs to get ahead or are just considered a liability rather than an asset to a fellow pilots company, well you may find yourself on the outside looking in.

 

Well said. On the flip side: I've noticed a lot, not all, of our current generation of pilots are self servant and not afraid to behave in said manner listed above on the other side of the coin. Especially as a Vet standing up for value of labor and safety for common core values against management.

 

Sure, but in my experiences on the civilian side, military guys seem to be pushed to the front of the line.

I'm not jealous, I can see why. The product and loyalty factor is predictable and it makes sense. To become a military pilot you are really put through the ringer, and not everyone passes. On the civilian side you can bust every check ride and still get the same license. Sure there are some self-servant indulged know-it-all types as within any demographic, but the product is more predictable.

Just my observation.

 

The following flights were canceled Monday Oct 19th, rescheduled to the following day. FlightAware says all of these flights were MD-80/83 aircraft but the problem might have been aircrew staffing instead of maintenance issues on some of them.

Maybe the company motto should be "We'll get you there eventually".
-----------------------------------------------------------------------------------

Travel Advisory

We thank you for flying and choosing us here at Allegiant, where "Travel is our Deal".



October 19, 2015

Flight 222 originally scheduled to depart Bellingham, WA to Las Vegas, NV on October 19, 2015 will now be operating as flight 5222 on October 20, 2015. The new scheduled time of departure out of Bellingham, WA is 4:23 PM, arriving in Las Vegas, NV at 6:56 PM.

Flight 223 originally scheduled to depart Las Vegas, NV to Bellingham, WA on October 19, 2015 will now be operating as flight 5223 on October 20, 2015. The new scheduled time of departure out of Las Vegas, NV is 1:00 PM, arriving in Bellingham, WA at 3:33 PM.

Flight 672 originally scheduled to depart Sanford, FL to Portsmouth, NH on October 19, 2015 will now be operating as flight 5672 on October 20, 2015. The new scheduled time of departure out of Sanford, FL is 10:00 AM, arriving in Portsmouth, NH at 12:51 PM.

Flight 673 originally scheduled to depart Portsmouth, NH to Sanford, FL on October 19, 2015 will now be operating as flight 5673 on October 20, 2015. The new scheduled time of departure out of Portsmouth, NH is 1:36 PM, arriving in Sanford, FL at 4:43 PM.

Flight 860 originally scheduled to depart St. Pete, FL to Lexington, KY on October 19, 2015 will now be operating as flight 5860 on October 20, 2015. The new scheduled time of departure out of St. Pete is 2:45 PM and arriving in Lexington at 4:41 PM.

Flight 861 originally scheduled to depart Lexington, KY to St. Pete, FL on October 19, 2015 will now be operating as flight 5861 on October 20, 2015. The new scheduled time of departure out of Lexington is 5:26 PM and arriving in St. Pete at 7:21 PM.

Flight 1208 originally scheduled to depart Asheville, NC to West Palm Beach, FL on October 19, 2015 will now be operating as flight 5208 on October 20, 2015. The new scheduled time of departure out of Asheville, NC is 2:00 PM, arriving in West Palm Beach, FL at 3:47 PM.

Flight 1209 originally scheduled to depart West Palm Beach, FL to Asheville, NC on October 19, 2015 will now be operating as flight 5209 on October 20, 2015. The new scheduled time of departure out of West Palm Beach, FL is 4:37 PM, arriving in Asheville, NC at 6:25 PM.

 

The PIE and SFB base have both 80's and AB in them so they could have been 80's, but last I checked BLI is an AB base so flt 222 and 223 would have been AB. Unless BLI has 80's that I don't know about.

 

FlightAware shows Allegiant flight 222 to consistently be flown by an MD-80 type, I suppose they could have an error in their database. I think you are right, another website (FlightRada24) shows the aircraft type to be an A319. I thought these kind of websites determined the aircraft type by using the aircraft tail number and matching it to a list of registration numbers with other info, but looks like they have a goof at FlightAware.

https://flightaware.com/live/flight/AAY222/history

.

 

I am on the AB and we do have mx issues, just not ones that make the news. I've noticed that when an AB can't go they rescue it with an 80. So even though not many AB flts get cancelled we do still have mx issues.