LAX95FA272 · Rockwell 112TC
Rockwell 112TC · Accident: airframe, component or system failure during landing
From McClellan-Palomar Airport (CRQ) to Whiteman Airport (WHP)
Event
- NTSB case
- LAX95FA272
- 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
- 2 · all aircraft and ground
- Ground fatalities
- 0
- 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 112TC
- 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
- N4569W
- Operator
- Jeffery Albrecht
- Onboard fatalities
- Unknown
- Route
- From McClellan-Palomar Airport (CRQ), Carlsbad, CATo Whiteman Airport (WHP), 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
- 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
- Airframe, component or system failure
- 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
- Utility pole; Wire, transmission
- 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 › Remedial action, delayed
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The aircraft touched down but did not slow during rollout. The aircraft drifted to the right edge of the runway three times and puffs of smoke were seen in the area of the main landing gear. After rolling the length of the runway and entering the displaced threshold at the end of the runway, the pilot attempted to abort the landing. On the initial climb, the aircraft struck a light pole, overhead utilities, and then crashed into a building. An inspection of the turbocharger, brake system, and powerplant controls revealed no conclusive discrepancies.
Probable cause
an undetermined aircraft system malfunction, and the pilot's delayed remedial action in response to insufficient braking action and/or inability to control engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX95FA272
- Event ID
- 20001207X03983
- Case number
- LAX95FA272
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1995-07-29.
- API snapshot SHA-256: e58d5c87d82cb7959bee53e3dcf5536a9bb399777d54906e748b6655fe398104; retrieved 2026-09-20T23:41:05.401Z.