Runway

October 31, 2006 - 10:01am

Last month, the FAA followed up on a March 11 e-mail, warning pilots about lax departure operations at Teterboro Airport (TEB), N.J. The latest e-mail graphics cover the Teterboro 5 IFR departure from Runway 24 and the Dalton VFR departure from Runway 19. (See www.ainalerts.com/ ainalerts/R24_T5A_Dalton.pdf.)

October 31, 2006 - 5:42am

Learjet 25, Amarillo, Texas, July 1, 2005–Landing at Amarillo International Airport with a 17-knot crosswind, the 7,300-hour captain was unable to maintain directional control of the Air America Jet Charter Learjet. The airplane struck a runway distance marker and ran off the runway to the left. The left wingtip tank fuel load was 200 to 300 pounds heavier than the load in the right wingtip.

October 31, 2006 - 5:28am

Cessna CitationJet CJ2 525A, Newnan, Ga., July 15, 2005–The NTSB said the CitationJet’s collision with a localizer antenna was caused by the pilot’s delay in aborting the landing and his failure to maintain obstacle clearance. The Safety Board listed as contributing factors hydroplaning and the localizer antenna.

October 31, 2006 - 5:05am

Commander 690A, Cleveland, Ohio, Jan. 4, 2005–The pilot’s failure to maintain directional control during landing caused the airplane to run off the runway and hit a sign, said the NTSB. While landing on Runway 24 at Cuyahoga County Airport, the Aero Commander began to yaw to the right, and the airplane ran off the runway.

October 31, 2006 - 5:03am

Challenger 600, Tupelo, Miss., March 9, 2005–Inadequate design of the STCed microphone jack assembly, resulting in restricted aft movement of the control column, was blamed for the accident of Romeo Mike Aviation’s Challenger.

October 31, 2006 - 5:02am

Beech King Air 200, Bay View, Texas, Dec. 10, 2004–The ATP pilot’s failure to maintain directional control as a result of his improper runway selection was blamed for the Charter One King Air’s crash into trees on takeoff from Rancho Buena Vista Airport. The right quartering 14-knot tailwind was a contributing factor. The runway was a 3,500-foot grass strip.

October 31, 2006 - 5:00am

Dassault Falcon 20, Pine Bluff, Ark., Dec. 5, 2004–The NTSB determined the probable cause of a Falcon 20 overrun was the pilot’s misjudgment of speed and distance. Contributing factors were the moderate rain and the reported encounter with hydroplaning conditions.

October 31, 2006 - 4:40am

Airport surface detection equipment model X (ASDE-X), designed to help controllers spot potential runway collisions, will be installed at 15 airports beginning with Seattle-Tacoma International Airport next month.

October 25, 2006 - 4:47am

Three serious near collisions on runways in Boston, New York and Las Vegas this year prompted the NTSB again to press for quicker action by the FAA to reduce such incidents. This issue has been on the Safety Board’s “most wanted” list since the list’s inception in 1990.

October 24, 2006 - 10:56am

Bombardier Challenger 600, Tupelo, Miss., March 9, 2005–The pilots of Romeo Mike Aviation’s Challenger 600 aborted the takeoff from Runway 36 of Tupelo Regional Airport and the nosegear collapsed. The airplane went off the departure end of the runway and was substantially damaged. The ATP-rated pilot and copilot and five passengers were not injured.

 
X