A little heavy? Try having LBA as your local. That touchdown was nothing! 😀
Paul
With HOU and MDW as to of their major hubs SWA has some short runways to land on. The longest runway at MDW is 1000′ shorter than LBA.
http://en.wikipedia.org/wiki/William_P._Hobby_Airport
http://en.wikipedia.org/wiki/Chicago_Midway_International_Airport
I would venture a guess that either a tire blew or the brakes locked on landing. The landing didn’t appear to be excessively hard, perhaps just a bad tire.
Interesting differences Deano. In the US we have no total Duty limits butwe are limited to 14 hours scheduled but it can be extended out to 16 hours for wx and mx. Flight time limits are 8 hours scheduled per duty period, 30 hours in a rolling 7 days, 100 hours per month and 1000 hours per year. International operations have slightly different hour limits. The 8 hours scheduled isn’t a limitation once you’ve begun your day. They saying is “legal to start, legal to finish” which means if you have delays you can fly as many hours as it takes to finish the flights as long as you don’t exceed your duty day limit. My record is 10 hours in 1 duty period thanks to thunderstorms and diversons.
Rest requirements are that we must get 8 hours between duty periods. Most airline pilot groups have negotiated slightly improved rules but not much. Our min rest is 9 hours but we can be scheduled for 8 hours if we are given 11 hours of compensitory rest during our next rest period. Nothing like the promise of future rest to make you feel better now. 😉
There are also continuous duty nights as well which go by many names depending on the company (standup overnights, illegals, etc.). Where the “rest period” is less than 8 hours so it isn’t considered a legal rest period so the whole night you are considered “on duty”. This is legal as long as you aren’t scheduled more than 14 hours of total duty time. You fly to the overnight, go to the hotel and grab a nap for a few hours and return to fly home. It’s been years since I’ve done them but I do remember quite clearly that they are absolutely miserable.
I don’t have any personally experience with a SODA and the only one’s any classmate carried was for color blindness. My guess is that it would be tough to get a SODA for anything other than a 3rd class medical for something of this type. Honestly the easiest and most accurate answer would come from a quick phone call to your AME.
This is probably a topic for the General Aviation forum too.
But I don’t like the reasoning: close to 100hrs a month => fatigue. That conclusion is drawn in that article.
I don’t think any conclusions were stated in the article, only outlining the legal and company flight time limits per month.
You can have 100 duty hours a month without having 14 hrs a day. Actually, if they fly 10 block hours with 20 hour off in between, it is 5 trips a month.
The limit is 100 FLIGHT hours, not duty hours, an important distinction. A crew can take a several hour delay for maintenance or weather before even pushing off the gate to start their flight. Every hour of delay on the ground extends there duty day while the flight time will remain unchanged.
There is difference between total flight time per month vs. duty time. I probably do 30-35 hours of duty a week for 20-23 hours of flight time per week. My duty time for the month is over 120 hours while the flight time is <100 hours.
As all people survived there is plenty of possibility to find out if crew was deprived of sleep. So I guess we’ll wait for the report to tell if the crew did remain
– within legal limits
– within commonly acceptable human limits (which I would consider at least 10 hours, preferably 12 hours between two shifts)[/QUOTE]
But if there is a limit of 100 hours monthly, and Emirates stays below it, where is the problem?
Obviously you don’t fly professionally nor understand what leads to fatigue. Fatigue isn’t a culmination of a months work of flying, it’s a result of events leading up to an event, hours perhaps a day before. How many hours off duty did this crew get prior to the flight in question? How many of those hours were restful? Did the hotel hold a Cinco de Mayo event outside the crews rooms leading to no sleep on there part?
Legal limitations don’t guarantee a rested crew unfortunately. Legally a crew only has to have 8 hours of rest between duty days (domestic US). Now that 8 hours isn’t really rest but 8 hours of not being on duty which is roughly from the time the door opens to 30 minutes before the next flight leaves the next day. Now the crew has to be transported to and from the hotel, check in, eat, go to bed, wake up, great ready for the new day, etc. I’ve had van rides from 2 minutes up to 30 minutes one way to the hotel. That 8 hours can easily, and legally, be nothing more than 6 hours of actual rest. Legally a crew can be scheduled for 14 hours of duty, 8 hours of rest followed by another 14 hours of duty not to mention that duty days can be extended to 16 hours for weather and maintenance. I’m sorry, but rest/duty rules suck and do little to insure a rested crew.
Fatigue is rarely used “magically” by crews. I can’t think of another accident where fatigue was mentioned by a crew as a cause. Given your attitude towards it you must have quite a list though so please share.
I can hardly believe fatigue is reason for someone to mess up his take-off speed calculation. If you fly an aircraft and have some experience, you should have a “mind-map” of take-off speeds and thrust settings (FLEX correction). You wouldn’t necessarily guess it, but some numbers might look suspicious.
In the A340-500 case the crew tried to take-off with very limited thrust under full load on a hot day. That is not fatigue, that seems to be lack of airmanship.
Fatigue can do amazing things. CFIT’s are a perfect example. No pilot would intentionally fly their airplane into the ground. If something as severe as that can happen due to fatigue a simple error in button pushing is nothing.
I guess it pays to sit when the seat belt sign is on.
So lets be sceptical for a moment. Lets say it’s possible that the sparks came from maybe something on the wing mechanics or one of the gears, maybe it was something to do with the flap motors and so the flaps weren’t extended enough and hense the long unexpected take-off because something happened after V1.
Might be cltching at straws here but just a thought to give the claims some credability.
The aircraft would have to be pretty significantly banked to strike portion of the wing or engine. As for something else sparking on the wing or in an area that would have been visible from inside the aircraft I can’t think of anything other than possibly something with an engine. I’m sure any damage in addition to the tailstrike would have also been reported and none was.
Having spent sometime in the middle seat of a widebody I leery of any eyewitness from that vantage point. It’s hard to see the window from that far away let alone describe what’s happening on the other side of it. Plus if something as dramatic as sparks flying passed windows 20-30″ forward of the tail strike I pretty sure we would have eyewitness reports from someone actually sitting at a window. Stuff like that is prime for any media report of such an event. None have surfaced except from someone sitting in the worst possible vantage point.
I wouldn’t be surprised if the Mangements powerplay here has something to do with being in contract negotiations with their pilots for 5 years now. Nothing like dinging a pilot at a Union sponsered event to send a message.
It’s pretty common to have language in the FOM that limits employees to wearing their uniforms to and from work only. It’s unwritten but I’d believe most managements would give employees some leeway so not to punish someone for dropping their kids off at school or something similar in uniform. The intent of the rule is to prevent someone from actively doing something non-work related in uniform (ie shopping). Why AirTran went after this pilot is odd. How did they find out he was there and how did it get into the news? There might be more to the story.
Here are the pictures of the damage from the tailstrike.



As you can clearly see the beginning of the damage appears roughly below where the last window sits. Even someone sitting at that window would be hard pressed to see sparks due to the curvature of the fuselage let alone someone not sitting at a window 10-15 rows/30’+ forward of that.
You weren’t even sitting by the window and saw them? Where were these sparks coming from that they would be visible especially if you weren’t sitting at the window? You weren’t even in the last row but the last 10-15 rows? You saw the sparks before you even felt the strike?
How in the world did were any sparks even as far up as that on the airplane? Do you have any idea how far rearward the tail skidplate is located from where you were actually sitting? Even an exploding engine doesn’t throw fire forward, only aft.
None of this is matching up. I’m thinking you saw light from something non-related and associated it with the tailstrike.
Nah, I still don’t believe it. The fuselage is 17′ wide which means the drag point is 8.5′ from the window. Due to the angle of view allowed from the window I would venture a guess that someone wouldn’t be able to see directly down so the sparks would have to spread another 5′ or so just to be seen by someone straining their neck to look straight down. Add to that that the strike point is roughly under the last row of seats on the A340 which means the sparks are at their narrowest point anyway. So how would a tailstrike produce a 30′ wide shower of sparks at the contact point to be viewable by someone sitting inside?
Here’s a pretty good video showing a tailstrike test in a MD-80. Even on that aircraft type you can see how far aft the shower of sparks really are.
http://www.youtube.com/watch?v=X7daNgAVtzc
Eyewitnesses involved in accidents or incidents are prone to incorrect testimonies due to the stress of the situation.
Maybe I’m being thick, but I still don’t understand how anyone could see sparks trailing at high speed backwards and underneath the tail of the aircraft.
I’m with you on this. I’m sure passengers heard/felt the tail strike but seeing a shower of sparks? I raise my BS flag on that one.
Quite a severe porpoising between the first hit and the one that resulted in the left wing striking the ground. From the wx report it was a bit windy but nothing severe at least nothing that has caused accidents before. As always, it’ll be interesting to discover what transpired during this accident.
On a side note, seeing that you’re going from DTW-DCA Future Pilot I would recommend trying to get a window seat on the left side of the airplane and hope for winds out of the south for landing for the best view. 🙂