PPRuNe Forums - View Single Post - MD-83 RTO Overrun at KYIP
View Single Post
Old 24th Mar 2017, 01:04
  #34 (permalink)  
Airbubba
 
Join Date: Jun 2001
Location: Rockytop, Tennessee, USA
Posts: 5,898
Likes: 0
Received 1 Like on 1 Post
Originally Posted by bafanguy
The split is very common. I lost track of the number of times I explained that to nervous pax. ;-)
Thanks, I flew the mighty DC-8 a long time ago but have never flown the DC-9 variants.

Originally Posted by safetypee
I recall a similar DC 9 / MD incident many years ago. The pre takeoff control check was completed at the hold; take off clearance was given to 'quickly' follow the departing aircraft, such that the departing jet blast disturbed debris / stones which jammed the elevator which was not detected until rotate.
The Mad Dog mishap that you describe was perhaps the 1970 ATI DC-8 crash at JFK:

https://aviation-safety.net/database...?id=19700908-1

https://www.fss.aero/accident-report...09-08-2-US.pdf

Executive Summary:

A Trans International Airlines Douglas DC-8-63F, K4863T, Ferry Flight 863 crashed during takeoff at John F. Kennedy International Airport, New York, at 1606, September 8, 1970.

Approximately 1,500 feet from the initiation of the takeoff roll , the aircraft was observed rotating to an excessively nose-high attitude. The aircraft became airborne about 2,800 feet down the runway after which it continued to rotate slowly upward to an attitude estimated to be between 60' and 90' above the horizontal, at an altitude estimated to be between 300 to 500 feet above the ground. The aircraft rolled about 20' to the right , rolled back to the left until it reached approximately a vertical angle of bank, and then fell to the ground in that attitude. The aircraft was destroyed by impact and postimpact fire. All 11 crewmembers, the only occupants of the aircraft, died in the accident.

The Board determines that the probable cause of this accident was a loss of pitch control caused by the entrapment of a pointed, asphalt-covered object between the leading edge of the right elevator and the right horizontal spar web access door in the aft part of the stabilizer. The restriction to elevator movement, caused by a highly unusual and unknown condition, was not detected by the crew in time to reject the takeoff successfully. However, an apparent lack of crew responsiveness to a highly unusual emergency situation, coupled with the captain's failure to monitor adequately the takeoff, contributed to the failure to reject the takeoff.

The Board has recommended to the Federal Aviation Administration that all DC-8 operators be advised of the circumstances of this accident; that takeoffs in DC-8's should be rejected when premature or unacceptable rotation of the aircraft occurs during takeoff; and that provisions for the detection of jammed elevators and determination of elevator position be provided to DC-8 crews.

The FAA replied that engineering evaluations are being completed and they will advise the Board of the results. The FAA also requested further data regarding the recommendation that takeoffs should be aborted when premature or unwanted rotation was experienced in the DC-8.

The Board also recommends that a review should be conducted on the subject of rejected takeoff procedures in air carrier operation with a view to amplifying, clarifying, and standardizing each pilot's role in that procedure. More specific information regarding the dynamics of rejected takeoffs and pre-takeoff briefings should also be considered.
https://www.fss.aero/accident-report...report_key=102

Obviously, the DC-8 tail is different from the DC-9 and MD-80 series tails, e.g. two jackscrews instead of one for example. But I believe the control tabs are similar.

Seems like there was an elevator control check on taxi out in the DC-8 where the FE announced 'drop-rise, drop-rise' (or 'double drop-rise' at United I believe). Also, I think the yoke was cycled in pitch at 80 knots on the takeoff roll to ensure that a foreign object had not caused a jam as in the JFK crash.
Airbubba is offline