Schweizer 269C accident near Manhattan, Kansas, November 18, 2005
On November 18, 2005 at about 8:30 pm local time, a Schweizer 269C (helicopter), registered N400PD, was substantially damaged in an accident near Manhattan, Kansas. It was a public-use flight under public-use (government) rules. No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The binding of the main rotor blade's tachometer cable during cruise flight resulting in an observed split tachometer indication/aural alarm and perceived mechanical emergency and the unsuitable terrain the pilot encountered during the emergency landing. A factor was the rocky terrain.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 18, 2005 · about 8:30 pm local time
- Place
- Manhattan, Kansas · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Schweizer 269C · all 269Cs on the register
- Registration
- N400PD · no longer on the register · serial S1833
- Damage
- Substantial damage
- Flight
- Public-use flight · public-use (government) rules
The NTSB's narrative final · quoted from the NTSB record
During a public use solo instructional flight the helicopter sustained substantial damage when it nosed over in a rocky, uneven field during a precautionary landing following an observed split in rotor/engine tachometer readings and an audible low rotor rpm alarm in cruise flight. The pilot perceived a mechanical emergency and performed a precautionary landing. The control box, tachometer cable, and tachometer were examined. The control box warning circuitry was not operational when first checked and operated after repair of an open circuit found on the circuit board. No anomalies were detected with the tachometer. Visual examination of the cable revealed indications of excessive wear and possible binding with windup of the outer strands. Binding of the cable is consistent with a bouncing tachometer needle.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 236 hours in all; 56 in this make and model
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 2,253.4 hours
- Last inspection: 100-hour inspection, November 1, 2005; 0 hours since
- Maximum gross weight: 2,150 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming HIO-360-D1A (piston); 0 hours total
The flight
- Departed from: TOP Topeka KS at 7:30 pm
- Destination: EMP Emporia KS
- Flight plan: VFR
Weather at the time
- Light: daylight
- Wind: from 220° at 12 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 55°F (13°C), dew point 32°F (0°C)
- Altimeter: 30.13 inHg
- Observation at 8:52 pm from MHK, 7 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.