FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX06FA133 · Rockwell 112 TCA

30 Mar 2006 · La Canada, CA, United States

Rockwell 112 TCA · Accident: loss of control in flight en route

From Santa Monica Municipal Airport (SMO) to North Las Vegas Airport (VGT)

Report a problem

Event

NTSB case
LAX06FA133
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
1 · 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

Rockwell 112 TCA

Aircraft type
Rockwell 112
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
N4641W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Santa Monica Municipal Airport (SMO), Santa Monica, CATo North Las Vegas Airport (VGT), North Las Vegas, NV
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
En route · climb to cruise
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 in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall/spin
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › Airspeed, not maintained
  • Pilot in command › Stall/spin, inadvertent

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 was receiving VFR flight following services from Air Traffic Control and was climbing to his cruise altitude of 9,500 feet when he requested information regarding the tops of the clouds. The pilot stated that he was VFR, and had gone through some clouds. The controller informed the pilot that he was in an area of intermittent radar coverage, and asked him if he was able to maintain VFR. The pilot replied that he could, and that he was at 6,800 feet. A few seconds later, the controller lost radar and radio contact. No distress call was received and an over-flying airplane tried unsuccessfully to establish radio contact. Radar data indicated that a target in the vicinity of the accident site appeared to make two left 360-degree turns. A witness saw the airplane come spiraling out of the bottom of the clouds with the nose pointed straight towards the ground. No preimpact mechanical malfunctions or failures were identified in the wreckage. Two weeks prior to the accident, the pilot had extensive surgery to remove a recurrent tumor in his maxillary sinus. At the time of the accident, the pilot was returning home from a post-surgical meeting at which the surgeon informed the pilot that some tumor remained in his eye socket. The pilot's options would be radiation to the eye, additional surgery to remove the floor of the eye socket and possibly the eye as well, or watch the tumor grow prior to taking any action. The pilot had likely recovered from most of the immediate effects of that surgery. The pilot had ibuprofen in his blood, suggesting that he had some continuing pain or discomfort, which might have reduced his attention to flight related tasks. He might also have been distracted or depressed by the prospect of additional surgery and/or the possible loss of one eye. His decision to fly or respond to events during flight could have been sub optimal due to post surgical issues.

Probable cause

The pilot's failure to maintain aircraft control and an adequate airspeed during climb to cruise that led to a stall/spin. Contributing to the accident were the clouds and the pilot's physiological state.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX06FA133
Event ID
20060404X00384
Case number
LAX06FA133
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: 4b7322b20d276eec8b1bdaf65b508e551d725037df8010e3d938bb25744cc91d; retrieved 2026-09-20T17:26:46.765Z.