Cessna T210N incident near Lubbock, Texas, November 9, 2008
On November 9, 2008 at about 8:06 pm local time, a Cessna T210N, registered N6267Y, suffered minor damage in an incident during initial climb near Lubbock, Texas (Lubbock Preston Smith Int'L airport). It was a personal flight under general aviation rules (Part 91). 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
An unidentified anomaly within the airplane's electrical system. Contributing to the incident was the pilot's failure to manually extend the landing gear.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 9, 2008 · about 8:06 pm local time · cases in 2008
- Place
- Lubbock, Texas · Lubbock Preston Smith Int'L · cases near this airport · map
- Type
- Incident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna T210N · all T210Ns on the register
- Registration
- N6267Y · registry record · serial 21064313
- Damage
- Minor damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
Shortly after takeoff and after raising the landing gear, the electrical components on the airplane started shorting out. The pilot heard "electrical noises" in his headset and smoke entered the cockpit. The pilot turned off nonessential electrical items, declared an emergency with air traffic control, and returned to land. During the approach he cycled the master switch off, then back on, to lower the flaps and gear. He placed the landing gear lever down, but did not attempt to manually lower the gear. During landing the landing gear collapsed, resulting in a scraped underbelly, which was initially reported as substantial damage. The airplane had a previous history of electrical malfunctions and anomalies after a global positioning navigation system was installed in the airplane. After the incident, repairs were made to remove excessive electrical wiring, correct multiple wire splices, reroute wiring, and replace bad connector pins. The source of the electrical anomalies could not be determined.
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
What happened, in order
- Unknown or undetermined during prior to flight
- Electrical system malf/failure during initial climb defining event
- Fire/smoke (non-impact) during initial climb
- Landing gear collapse during landing (flare/touchdown)
The NTSB's findings
- cause Aircraft › Aircraft systems › Electrical power system › (general) › Malfunction other cases naming the electrical power
- Aircraft › Aircraft systems › Landing gear system › (general) › Malfunction other cases naming the landing gear
- factor Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instrument: airplane
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 1,902 hours
- Last inspection: annual inspection, November 29, 2007; 49 hours since
- Seats: 6
- Landing gear: retractable
- Engine: Cont Motor TSIO-520 SER (piston); 0 hours total
The flight
- Departed from: LBB Lubbock TX at 8:00 pm
- Destination: CVN Clovis Municipa NM
- Flight plan: none
- Runway 17R, 11,000 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: from 170° at 12 knots, gusting 23
- Visibility: 10 statute miles
- Sky: a few clouds at 4,500 ft
- Temperature: 64°F (18°C), dew point 43°F (6°C)
- Altimeter: 29.79 inHg
- Observation at 7:53 pm from KLBB
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
4 documents, released by the NTSB on July 22, 2009. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Statement of Party Representatives to NTSB Investigation | PDF, 1 page | View Download |
| 3 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 1 page | View Download |
| 4 | Maintenance Documents | PDF, 7 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N6267Y on the register today · the tail number may have moved to another aircraft since
- Cessna T210 Turbo Centurion 1,280 registered today · the model family and its accident history
- Cessna 72,672 aircraft on the register
- Engine: Cont Motor TSIO-520 SER 4,110 aircraft carry this series today · as the NTSB recorded it
- Lubbock Preston Smith International · nearest airport
- Clovis Regional · bound for
- Accidents and incidents in Texas 6,244 since 1982 · 1,061 in the last ten years
- Texas 29,992 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN09IA057.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
