corjulo
Line Up and Wait
I alway thought this was an aviation urban legend, that no one could miss a control lock. Well, was I amazed when I learned that my own club's last plane was a victim to this.
ASF Accident Details
NTSB Number: NYC96LA129
Aircraft and Flight Information
Make/Model CESSNA / 172
Tail Number N1665Y
Airport BID
Light Conditions Day
Basic WX Conditions VMC
Phase of Flight Takeoff
AOPA Members can click on the airport identifier (if provided) to see the airport diagram and approach charts.
Narrative Type: NTSB FINAL NARRATIVE (6120.4)
The pilot conducted a preflight inspection, then began his planned departure. During the takeoff roll, the control wheel would not move aft, and the airplane continue off the departure end of the runway. During the runway overrun, the pilot attempted to select a path of minimum obstruction ahead. Subsequently, the airplane encountered brush and came to rest inverted. Postaccident examination of the airplane, revealed the control lock was installed. When questioned about the installed control lock, the pilot stated, 'that would explain it.'
Narrative Type: NTSB PRELIMINARY NARRATIVE (6120.19)
On June 23, 1996, about 1935 eastern daylight time, a Cessna 172C, N1665Y, was substantially damaged when it overran the runway and nosed over during takeoff at the Block Island State Airport, Block Island, Rhode Island. The private pilot and passenger were seriously injured. Visual meteorological conditions prevailed for the personal flight destined for the Hartford-Brainard Airport, Hartford, Connecticut. No flight plan was filed for the flight conducted under 14 CFR Part 91.
In a written statement submitted by the pilot, he stated:
"As a background, my wife. . .and I departed Hartford-Brainard Airport about [1330]. . .for Block Island. The aircraft was owned by The Civil Air Patrol Flying Association Inc. of which I am a member. The flight to Block Island was uneventful. . . .Sometime shortly after [1900], we returned to the airplane, completed the prefight, and taxied to the end of runway 28 for the runup. During the take-off roll, I only recall that: 1) at normal rotation speed, I noticed that the control wheel would not travel aft and I did not understand why it would not travel further; 2) as I approached the end of runway, I realized we would not clear and I attempted to select a path of minimum obstruction ahead of the aircraft. . . ."
Examination of the wreckage by a Federal Aviation Administration Inspector revealed no evidence of malfunctions, nor did the pilot report any. Also, the control lock was observed to be installed.
Following the wreckage examination, a telephone interview was conducted with the pilot. During the interview, the pilot was asked if he was aware that the control lock was found installed at the accident site. He stated that he had been aware of the finding and stated, "that would explain it."
According to the Cessna 172 Pilot Operating Handbook, for preflight inspection, it stated to remove the control lock.
Narrative Type: NTSB PROBABLE CAUSE NARRATIVE
the pilot's inadequate preflight, by failing to remove the control lock and checking the flight controls before takeoff, and his failure to abort the takeoff in a timely manner, which resulted in an overrun, an encounter with brush, and a subsequent nose over of the airplane.
ASF Accident Details
NTSB Number: NYC96LA129
Aircraft and Flight Information
Make/Model CESSNA / 172
Tail Number N1665Y
Airport BID
Light Conditions Day
Basic WX Conditions VMC
Phase of Flight Takeoff
AOPA Members can click on the airport identifier (if provided) to see the airport diagram and approach charts.
Narrative Type: NTSB FINAL NARRATIVE (6120.4)
The pilot conducted a preflight inspection, then began his planned departure. During the takeoff roll, the control wheel would not move aft, and the airplane continue off the departure end of the runway. During the runway overrun, the pilot attempted to select a path of minimum obstruction ahead. Subsequently, the airplane encountered brush and came to rest inverted. Postaccident examination of the airplane, revealed the control lock was installed. When questioned about the installed control lock, the pilot stated, 'that would explain it.'
Narrative Type: NTSB PRELIMINARY NARRATIVE (6120.19)
On June 23, 1996, about 1935 eastern daylight time, a Cessna 172C, N1665Y, was substantially damaged when it overran the runway and nosed over during takeoff at the Block Island State Airport, Block Island, Rhode Island. The private pilot and passenger were seriously injured. Visual meteorological conditions prevailed for the personal flight destined for the Hartford-Brainard Airport, Hartford, Connecticut. No flight plan was filed for the flight conducted under 14 CFR Part 91.
In a written statement submitted by the pilot, he stated:
"As a background, my wife. . .and I departed Hartford-Brainard Airport about [1330]. . .for Block Island. The aircraft was owned by The Civil Air Patrol Flying Association Inc. of which I am a member. The flight to Block Island was uneventful. . . .Sometime shortly after [1900], we returned to the airplane, completed the prefight, and taxied to the end of runway 28 for the runup. During the take-off roll, I only recall that: 1) at normal rotation speed, I noticed that the control wheel would not travel aft and I did not understand why it would not travel further; 2) as I approached the end of runway, I realized we would not clear and I attempted to select a path of minimum obstruction ahead of the aircraft. . . ."
Examination of the wreckage by a Federal Aviation Administration Inspector revealed no evidence of malfunctions, nor did the pilot report any. Also, the control lock was observed to be installed.
Following the wreckage examination, a telephone interview was conducted with the pilot. During the interview, the pilot was asked if he was aware that the control lock was found installed at the accident site. He stated that he had been aware of the finding and stated, "that would explain it."
According to the Cessna 172 Pilot Operating Handbook, for preflight inspection, it stated to remove the control lock.
Narrative Type: NTSB PROBABLE CAUSE NARRATIVE
the pilot's inadequate preflight, by failing to remove the control lock and checking the flight controls before takeoff, and his failure to abort the takeoff in a timely manner, which resulted in an overrun, an encounter with brush, and a subsequent nose over of the airplane.