siucavflight
Back from the forsaken
- Joined
- Jul 30, 2003
- Posts
- 3,512
This is wrong
http://www.youtube.com/watch?v=V06LBgfuxgA&NR
http://www.youtube.com/watch?v=V06LBgfuxgA&NR
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Smellycat said:NTSB Identification: NYC05LA085.
The docket is stored in the Docket Management System (DMS). Please contact Records Management Division
14 CFR Part 91: General Aviation
Accident occurred Sunday, May 15, 2005 in Atlantic City, NJ
Probable Cause Approval Date: 5/30/2006
Aircraft: Cessna 525A, registration: OY-JET
Injuries: 1 Minor, 3 Uninjured.
The pilot performed "a low pass" over the runway, and then touched down approximately 1,000 feet beyond the approach end of the 2,948-foot long runway, with a tailwind of approximately 10 knots. After touchdown, the airplane continued off the end of the runway, and subsequently impacted water. According to the Cessna 525A Landing Distance Chart, an airplane with a landing weight of 11,400 pounds required 3,000 feet of landing distance, in a no wind situation. With a 10 knot tailwind, the airplane required 3,570 feet of landing distance. The published airport diagram for the airport, was observed attached to the pilot's control column after the accident. A notation, which read, "airport closed to jet aircraft" was observed on the diagram. Additionally, the same notation, "Arpt CLOSED to jet traffic," was observed in the FAA Airport/Facility Directory. Examination of the airplane revealed no mechanical deficiencies. The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The pilot's improper decision to plan a flight to a runway of insufficient length, his improper in-flight decision to land on that inadequate runway with a tailwind, and his failure to obtain the proper touchdown point. A factor in the accident was the tailwind condition.
Full narrative availableIndex for May2005 | Index of months postamble();
___________________________________________________
PILOT ERROR you think?
Learsforsale said:I always hated Bader field. I always go there with the best intentions, and I have never had a good experience there.
I cannot imagine trying to land a CJ2 there. I landed a Katana there with a slight tailwind, and I had to use the full length of the runway!
siucavflight said:
A review of the FAA Airport/Facility Directory for the Northeast U.S., revealed the following notation listed in the Airport Remarks section of the Atlantic City/Bader Field Airport entry, "Arpt CLOSED to jet traffic." Additionally, runway 11 was a 2,948 foot-long, 100 foot-wide, asphalt runway.
Additionally, the airport diagram for Bader Field, was observed attached to the pilot's control column after the accident. A notation, which read, "airport closed to jet aircraft" was observed on the diagram.
According to the Cessna 525A Landing Distance Chart, an airplane with a landing weight of 11,400 pounds required 3,000 feet of landing distance, in a no wind situation. With a 10 knot tailwind, the airplane required 3,570 feet of landing distance.
Jetz said:Keep your video cameras handy, folks. The VLJ's are coming!
Coool Hand Luke said:That was awesome. I had heard about this when it happend, but I wasn't aware that the engine restarted after everyone had evacutated. Wow.
wrxpilot said:I heard (ya, speculation) that the pilot evacuated the pax, restarted, and tried to make it back onto the a/p property. Makes more sense than the FADEC starting the engine(s) and throttling up.
That about made me crap my pants, funniest thing I have heard all day.Van Hooydonk said:The only way this could have been more entertaining, would be if Caneman would have done the narration. I can hear it now, "Pretty smoooooth landing....looks like he is going to take it for a wash"
wrxpilot said:I heard (ya, speculation) that the pilot evacuated the pax, restarted, and tried to make it back onto the a/p property. Makes more sense than the FADEC starting the engine(s) and throttling up.
wrxpilot said:Those gotta be some pretty stout engines though, can't imagine how much water erosion was in the turbine section after that. Anyone know the manufacturer on that model?
Fugawe said:See the full report link, says rt throttle was bent at the idle stop. Motor was probably running at idle the whole time, hard to tell in the video.
Folks in boat don't seem to notice motor until it starts to spool up. It might have been running at idle unnoticed or ignored. I'm sure it was very confusing and hectic out there.
That the pilot didn't fully shut the motor down doesn't surprise me.
Fugawe
TrafficInSight said:I don't think so. You can hear the engine spool and then light off. My guess is that it was not properly secured in the haste of evacuation and when the water started pouring in, bam.
TrafficInSight said:It would be nearly impossible not to notice a jet engine running 7 feet from your boat, even at idle. They've made progress with noise... but not that much progress![]()
HA HA!!!:laugh: :laugh:shamrock said:If it wasn't for the gear it probably would have made it on to the step.
No, but a lot of times the contactors, batteries, and other engine type equipment is in the "hellhole" between the engines... and that is in the water. My guess is that the pilot didn't secure anything in his haste to evacuate and when water hit the contactors....Fugawe said:I hear ya', but how does a motor go from dead stop to running because water started pouring in? I admit not knowing this jet -- fuel systems electric pumps? Ignitors? Multi-spool motor?
Doesn't look like motor is down in water prior to accelerating up. Not sure why it'd accelerate except perhaps water shorted an electronic controller somewhere.