SEA07CA146 · Cessna T210N
Cessna T210N · Accident: loss of control on ground/water during landing
From Rancho Murieta Airport (RIU) to Meadows Field (BFL)
Event
- NTSB case
- SEA07CA146
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna T210N
- Aircraft type
- Cessna 210
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N6973N
- Operator
- Joseph P. Baratta · private individual
- Onboard fatalities
- Unknown
- Route
- From Rancho Murieta Airport (RIU), Rancho Murieta, CATo Meadows Field (BFL), Bakersfield, CA
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control on ground/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Directional control, not maintained
- Pilot in command › Flare, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that as he was turning on to base leg for Runway 30R he noticed that the wind was stronger than anticipated, and when established on final the wind had caused the airplane to drift to the right of the runway's centerline. The pilot stated that as he was making adjustments to line up with the centerline the air traffic controller instructed him to go around. As he was pitching up and adding power the controller then told the pilot he was cleared to land, prompting the pilot to reduce power, drop the nose, and continue to make adjustments for the crosswind. The pilot reported that when the airplane touched down it bounced two or three times, "...then a strong wind gust caused the plane to exit the runway to the right." As a result of the nose wheel collapsing aft the firewall sustained substantial damage. The pilot estimated winds from 270 degrees between 12 and 14 knots, with wind gusts to 18 knots.
Probable cause
The pilot's improper flare, which resulted in a loss of directional control. Factors included the crosswind and gusty wind condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA07CA146
- Event ID
- 20070712X00930
- Case number
- SEA07CA146
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 0bf42b57bc888add1512269a351944bde7e59300b694c3110bf86d8e78ba8400; retrieved 2026-09-22T03:46:49.503Z.