FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX08CA095 · Curtiss-Wright Travel Air 4000

9 Apr 2008 · Carlsbad, CA, United States Narrative disagrees

Curtiss-Wright Travel Air 4000 · Accident: loss of control on ground during landing

From McClellan-Palomar Airport (CRQ) to McClellan-Palomar Airport (CRQ)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
LAX08CA095
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

Curtiss-Wright Travel Air 4000

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
N4418
Onboard fatalities
Unknown
Route
From McClellan-Palomar Airport (CRQ), Carlsbad, CATo McClellan-Palomar Airport (CRQ), Carlsbad, 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 · landing roll
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 on ground
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

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

NTSB narrative

Following an uneventful commercial air tour sightseeing flight in the 1928 model biplane, the pilot returned to the departure airport and prepared for landing on runway 24. The pilot stated that during his approach, air traffic control tower personal reported that the wind was from 180 degrees at 5 knots. The pilot compensated for the wind by initiating a crab, and he landed on the runway. During the landing rollout the pilot lost directional control of the airplane. The airplane's lower right wing impacted the runway as the airplane suddenly reversed direction and ground looped to a stop.

Probable cause

The pilot's inadequate crosswind compensation and failure to maintain directional control during landing rollout.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX08CA095
Event ID
20080508X00630
Case number
LAX08CA095
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: 82453ab09d0d6f0c383956c98cb8a5f0a4b8ce1ab7e9cee46512fb558610fd8c; retrieved 2026-09-15T09:38:00.145Z.