NTSB CAROL · Event
Event LAX96LA233
Registry · N444BG
FAA Aircraft Registry record.
Make / Model
CESSNA 421C
Year of manufacture
1980 · 16 years old at event
Engine
CONT MOTOR GTSIO-520 SER (435 hp)
Seats / Engines
8 seats · 2 engines
Last airworthiness date
20010801
ADS-B equipped
Yes — Mode-S A55999
Registrant of record
MITCHELL AVIATION LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
an engine compartment fire, which originated in flight from loose fuel and/or oil lines near the engine's firewall.
Factual narrative
HISTORY OF FLIGHT
On June 15, 1996, at 0823 hours mountain standard time, a Van Horn Velocity, N444BG, owned and operated by the pilot, experienced an in-flight fire. The pilot of the experimental homebuilt airplane declared an emergency and made a forced landing on rough terrain about 2 miles southwest of Goodyear, Arizona. According to the Federal Aviation Administration (FAA), during the landing the airplane collided with a pole, nosed over, and was destroyed by fire. The commercial pilot was fatally injured. Visual meteorological conditions prevailed during the personal flight, and no flight plan was filed. The flight originated from Goodyear at 0700. The National Transportation Safety Board reviewed recorded radio transmissions at the local control position in the Goodyear air traffic control tower for June 15, 1996, between 0815 and 0828 mountain standard time. The following summarizes pertinent transmissions. All listed times are accurate to within plus or minus 15 seconds. At 0820:40, the accident pilot reported that he was ". . . approximately ten miles west at four thousand feet with an engine problem." The pilot then declared an emergency and requested a landing clearance. The Goodyear controller immediately responded and cleared the pilot to land. In the pilot's next transmission, at 0821:30, he informed the controller that he had about 4 hours of fuel onboard. He also stated "but it doesn't seem to be working to well right now." The pilot estimated that he would arrive at the Goodyear Airport in about 5 minutes. At 0821:50, the pilot made his next transmission and stated "I've got a fire on board. I've a fire on bo . . ." (The complete transmission was not recorded or was interrupted.) The controller responded and stated the following: "Roger I understand you have a fire on board. Do you think you can make it to the airport?" (No reply was recorded.) At 0824:00, the controller said: "Four Bravo Golf you still with me?" Once again, no reply was recorded. At 0824:20, during a transmission to another individual, the controller indicated that she believed the airplane was down because she observed "fire out there and he is not talking to me." One minute later the controller reported observing black smoke which she estimated was about 2 miles southwest of the airport.
TESTS AND RESEARCH
On July 2, 1996, the airplane wreckage was examined by the FAA and a participant from Lycoming Engines. In summary, the FAA reported that the fire had been concentrated in the area of the firewall. Both fuel and oil lines were found loose with fire traces indicating both fuel and oil involvement. No specific point of origin was determined. The FAA noted that the engine had been "highly modified" from its original Lycoming factory design (see attached report).
PERSONNEL INFORMATION
According to the FAA, the pilot's total civilian flying experience was about 3,000 hours. The pilot's wife estimated that her husband's total flying experience was over 9,000 hours. Acquaintances of the pilot and family members reported that the pilot had a total of about 40 hours of experience flying in both his and other Velocities. Also, the pilot had flown his airplane the day preceding the accident. The pilot was in good health and did not take prescription medication. On June 17, 1996, an autopsy was performed by the Office of the Medical Examiner in Maricopa County, 120 S. Sixth Avenue, Phoenix, Arizona. According to the medical examiner, the pilot died as a result of multiple blunt force injuries. No ethanol was detected. While cruising at 4,000 feet during a personal flight, the pilot reported to the air traffic controller that he was about 10 miles from the airport, was experiencing an engine problem, and was declaring an emergency. About 1 minute later, he stated that he had a 'fire on board.' The pilot made a forced landing about 2 miles from the airport. During the landing, the airplane collided with a pole, then was destroyed by fire. Examination of the wreckage by an FAA inspector revealed that the fire had been concentrated in the firewall area. Fuel and oil lines were found loose, and the fire left traces of both fuel and oil involvement. No specific point of origin was determined. Investigation also revealed that the engine had been modified from its original factory design. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1996_LAX96LA233.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type. Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- arXiv 2026 · arXiv preprint
Velocity-Free Horizontal Position Control of Quadrotor Aircraft via Nonlinear Negative Imaginary Systems Theory
This paper presents a velocity-free position control strategy for quadrotor unmanned aerial vehicles based on nonlinear negative imaginary (NNI) systems theory.
- arXiv 2026 · arXiv preprint
Pitot-Aided Attitude and Air Velocity Estimation with Almost Global Asymptotic Stability Guarantees
This paper investigates the problem of attitude and air velocity estimation for fixed-wing unmanned aerial vehicles (UAVs) using IMU measurements and at least one Pitot tube measurement, with almost g…
- arXiv 2025 · arXiv preprint
Obstacle Avoidance of UAV in Dynamic Environments Using Direction and Velocity-Adaptive Artificial Potential Field
The conventional Artificial Potential Field (APF) is fundamentally limited by the local minima issue and its inability to account for the kinematics of moving obstacles.
- arXiv 2025 · arXiv preprint
A Nonlinear Observer for Air-Velocity and Attitude Estimation Using Pitot and Barometric Measurements
This paper addresses the problem of estimating air velocity and full attitude for unmanned aerial vehicles (UAVs) in GNSS-denied environments using minimal onboard sensing-an interesting and practical…
- arXiv 2024 · arXiv preprint
Critical velocity for wake vortex generation behind a plate in a superflow
We study theoretically the critical velocity $U_c$ for quantum vortex generation by a thin plate-shaped obstacle moving through a uniform Bose-Einstein condensate.
- arXiv 2023 · arXiv preprint
RRT and Velocity Obstacles-based motion planning for Unmanned Aircraft Systems Traffic Management (UTM)
In this paper, an algorithm for Unmanned Aircraft Systems Traffic Management (UTM) for a finite number of unmanned aerial vehicles (UAVs) is proposed.
Browse the full corpus — academia portal ↗