FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14CA295 · Cessna 414 UNDESIGNAT

16 Jun 2014 · Pleasanton, TX, United States

Ping Ze Aviation Cessna 414 UNDESIGNAT · Accident: loss of control in flight on approach

From Addison Airport (ADS) to Pleasanton Municipal Airport (PEZ)

Report a problem

Event

NTSB case
CEN14CA295
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 414 UNDESIGNAT

Aircraft type
Cessna 414
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
N1671T
Onboard fatalities
Unknown
Route
From Addison Airport (ADS), Addison, TXTo Pleasanton Municipal Airport (PEZ), Pleasanton, TX
Aircraft age
About 41 years (built 1973)
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
Approach · VFR go-around
Defining eventThe 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 in flight
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot obtained the airport's weather information prior to landing, which included wind from 250 degrees at 9 knots gusting to 20 knots. He realized that he would land with a 90 degree crosswind on either runway and elected to land on the runway 34. When the airplane was on short final, the pilot realized the wind had shifted to a direct tailwind and he immediately executed a go-around. The pilot established a 500 feet per minute climb at an airspeed of 120 knots. When the airplane was about 200-feet-above the ground, the airplane began to descend and the airspeed began to decrease. The pilot was unable to arrest the descent and lowered the airplane's nose in an attempt to gain airspeed, but the airplane stalled and rolled left The pilot leveled the wings and the airplane impacted the ground in a level attitude, resulting in substantial damage to the airplane's fuselage and right wing. Wind reported five minutes after the accident was from 130 degrees at 14 knots gusting to 19 knots. The pilot reported there were no mechanical deficiencies with the airplane or engines that would have precluded normal operation prior to the accident.

Probable cause

The pilot's failure to maintain aircraft control during an aborted landing due to an encounter with a tailwind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14CA295
Event ID
20140617X55442
Case number
CEN14CA295
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. 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: d7d6e641b3492a3f859721833c88de52e5076f06410c36aebe5912b656503aaf; retrieved 2026-09-16T00:06:02.245Z.