Saturday, June 27, 2020

Thatcher CX4, N274DR: Accident occurred June 24, 2020 at Cable Airport (KCCB), San Bernardino County, California

Federal Aviation Administration / Flight Standards District Office; Riverside, California

Aircraft struck ground, nosed into ditch at end of runway.

Date: 24-JUN-20
Time: 18:45:00Z
Regis#: N274DR
Aircraft Model: CX4
Event Type: ACCIDENT
Highest Injury: UNKNOWN
Aircraft Missing: No
Activity: PERSONAL
Flight Phase: LANDING (LDG)
Operation: 91

UPLAND, California (KABC) -- It was a harrowing plane crash captured on video, and now the pilot who survived it recalls the frightening ordeal.

David Reser, 80, spoke to Eyewitness News about the moment the small plane he was piloting crashed while attempting to land at an airport in Upland Wednesday afternoon.

Reser faced two major problems. The propeller of the plane flew off and oil suddenly covered his windshield, forcing him to fly blind.

"It was a real surprise when the propeller went off. It came off the airplane, but I didn't have a sudden fear," he said. "I've always practiced off-field landings or deadstick landings. Now I get to do one."

"Mayday, Mayday! Just lost my propeller, there is oil all over the screen," Reser says in released audio tapes.

Reser relied on his 48 years of flying experience. Wanting to avoid homes in the area, he dove for the runway looking over the side to try to stay on course, but he was coming in too fast and too high. He knew he wasn't going to make the runway.

"My first thought was when the wingtip hit and it was starting to turn, I thought, 'So, this is the way you die, huh,'" he said. "That was the only thought I had."

AIR7 HD was over the scene as the aircraft hit the runway at Cable Airport, bounced into the air and came to a rest in a field.

The long-time pilot suffered minor injuries and was rescued from the plane by emergency crews after he was trapped in the cockpit.

He was seen shortly afterward walking around.

The Federal Aviation Administration says the aircraft was a homebuilt kit plane. His Thatcher CX4 took him six years to build.

Despite the close call, he says he can't wait to get back in the air.

"They always say any landing you walk away from is a good one," he said.

A single-engine aircraft went off the runway at Cable Airport in Upland after landing shortly before noon Wednesday, June 24. The pilot sustained minor injuries, authorities said.

There were no immediate reports of a fire or fuel leak, said Jimmy Schiller, a spokesman for the San Bernardino County Fire Department, which was called to the scene in the area of 2100 West Foothill Boulevard.

The pilot was the only person on board the Thatcher CX4 experimental aircraft, said Ian Gregor, a spokesman for the Federal Aviation Administration, which will investigate the crash. The FAA was notified around 11:45 a.m Gregor said.

Records show the plane is owned by a Fullerton man, who also is a licensed pilot. The pilot at the controls of the Thatcher CX4  was not identified as of Wednesday afternoon.

The pilot had to be freed from the aircraft before he could be taken to a hospital, Schiller said.

The experimental Thatcher CX4 aircraft, in the livery of a World War II “Flying Tiger” plane, was removed from the area by forklift-and-crane rig later in the day.

Beech 76, N6752Z: Incidents occurred June 24, 2020 and January 15, 2018 at Olive Branch Airport (KOLV), DeSoto County, Mississippi

Federal Aviation Administration / Flight Standards District Office; Jackson, Mississippi

June 24, 2020:  Aircraft lost directional control and veered off runway on takeoff roll.

Vector USA LLC

Date: 24-JUN-20
Time: 15:05:00Z
Regis#: N6752Z
Aircraft Make: BEECH
Aircraft Model: 76
Event Type: INCIDENT
Highest Injury: NONE
Aircraft Missing: No
Activity: PERSONAL
Flight Phase: TAKEOFF (TOF)
Operation: 91

January 15, 2018: Aircraft landed with nose gear retracted.

Date: 15-JAN-18
Time: 23:38:00Z
Regis#: N6752Z
Aircraft Make: BEECH
Aircraft Model: 76
Event Type: INCIDENT
Highest Injury: NONE
Aircraft Missing: No
Flight Phase: LANDING (LDG)
Operation: 91

Cessna 402C, N67909: Incidents occurred June 24, 2020 and June 16, 2017

Federal Aviation Administration / Flight Standards District Office; Boston, Massachusetts

June 24, 2020: Aircraft landed and smoke was coming from left engine. 

Hyannis Air Service Inc doing business as Cape Air

Date: 24-JUN-20
Time: 14:01:00Z
Regis#: N67909
Aircraft Make: CESSNA
Aircraft Model: 402
Event Type: INCIDENT
Highest Injury: NONE
Aircraft Missing: No
Damage: MINOR
Activity: CARGO
Flight Phase: LANDING (LDG)
Aircraft Operator: CAPE AIR
Flight Number: KAP929

BARNSTABLE — Firefighters were called to Barnstable Municipal Airport on Wednesday morning when smoke began coming out of a plane, a Hyannis Fire Department official said.

Firefighters were called to 125 Mary Dunn Way at 10:08 a.m. for an inflight emergency when a pilot saw smoke coming out of the Cessna 402C aircraft, Capt. Gregory Dardia said.

The pilot was the only person in the aircraft, and it was already on the ground when the incident started, Dardia said.

The Cessna 402 “blew its turbo,” causing oil to spill from the engine, landing on hot components and causing smoke, Dardia said.

There were no reported injuries. The aircraft was taken to the maintenance department at the airport to be fixed.

June 16, 2017:  Aircraft struck a fence with its wing.

Date:    16-JUN-17

Time:    12:15:00Z
Regis#:    N67909
Aircraft Make:    CESSNA
Aircraft Model:    C402
Event Type:    INCIDENT
Highest Injury:    NONE
Aircraft Missing:    No
Damage:    MINOR
Activity:    OTHER
Flight Phase:    UNKNOWN (UNK)

System/Component Malfunction/Failure (Non-Power): North American T-28B Trojan, N215SF; accident occurred August 23, 2018 at Anoka County-Blaine Airport (KANE), Minneapolis, Minnesota

The National Transportation Safety Board did not travel to the scene of this accident.

Additional Participating Entity:

Federal Aviation Administration / Flight Standards District Office; Minneapolis, Minnesota 

Aviation Accident Factual Report - National Transportation Safety Board:

Location: Minneapolis, MN
Accident Number: CEN18LA349
Date & Time: 08/23/2018, 1106 CDT
Registration: N215SF
Aircraft Damage: Destroyed
Defining Event: Sys/Comp malf/fail (non-power)
Injuries: 1 Serious
Flight Conducted Under: Part 91: General Aviation - Personal


The pilot stated that he received a generator failure annunciation while en route and decided to return to the departure airport. During the approach, the pilot opened the canopy after severe smoke entered in the cockpit. The pilot stated there was a heavy spray of fuel during the downwind leg of the approach that ignited during the base leg of the approach. During the final leg, when the airplane was about 150-200 ft above ground level, he determined that he could not reach the runway due to the severe fire. He pushed the airplane nose down about 20-25°, and the airplane impacted the ground short of the runway. The airplane was destroyed by impact forces and a postcrash fire. Postaccident examination of a fabric sample from the pilot's flight suit revealed stains that were consistent with hydraulic fluid. Postaccident examination of the airplane revealed the engine was separated from the airframe, and the propeller was separated from the engine. The propeller blades displayed features consistent with engine power. Fire consumed most of the cockpit area and underlying systems between the firewall and aft cockpit. Due to the fire damage, the ignition source and the flammable source could not be determined. The pilot did not perform an emergency shut down of the electrical system and/or engine after the generator failure annunciation as indicated in the airplane flight manual. However, the effect of the pilot not performing the airplane emergency procedures for smoke and fire is unknown because the timing in which the procedures would have to be performed, the flammable source location, and the kind of ignition source are unknown. 

Probable Cause and Findings

The National Transportation Safety Board determines the probable cause(s) of this accident to be:
The fire during approach for reasons that could not be determined based on the available evidence, which resulted in impact with terrain during approach for a precautionary landing.


Hydraulic power system - Not specified (Cause)
Hydraulic fluid - Not specified (Cause)

Personnel issues
Lack of action - Pilot

Not determined
Not determined - Unknown/Not determined (Cause)

Factual Information 

On August 23, 2016, at 1106 central daylight time, a North American T-28B, N215SF, experienced an in-flight fire during approach to runway 18 at Anoka County-Blaine Airport (ANE), Minneapolis, Minnesota. Smoke was seen trailing from the airplane before it descended and impacted the ground near the approach end of runway 18. The pilot sustained serious injuries and the airplane was destroyed by impact forces and a post-crash fire. The airplane was registered to Aviation Specialty LLC and was operated by the pilot under 14 Code of Federal Regulations Part 91 as a personal flight that was not operating on a flight plan. Visual meteorological conditions prevailed at the time of the accident. The local flight originated from ANE at 1030.

A witness stated that he was marshaling an aircraft at a fixed base operator located at the north end of the airport when he saw the T-28 coming in. He said the T-28 entered a "hard left turn," which "seemed standard for them." The airplane "seemed normal" as it was flying downwind and then "cut a little soon" than what he was used to seeing. He said the airplane performed S-turns toward the approach end of the runway, performed a slip and then may have stalled; it "seemed like it stalled." The airplane impacted on the north side of the runway, right wing first, and the airplane cartwheeled. The landing gear was in the extended position when the airplane turned onto the base leg. The engine sounded "normal."

The pilot stated while en route, he received a generator failure annunciation and decided to return to ANE. When he entered an overhead approach at ANE, he experienced severe smoke and he then opened the airplane canopy. During the downwind leg, he experienced a heavy spray of fuel. During the base leg, the fuel ignited, and he was engulfed in flames. He entered the final leg and about 150-200 feet above ground level, he determined that he could not attain the runway for landing due to the severe fire. He pushed the airplane nose down about 20-25 degrees and the airplane impacted the ground short of the runway.

The pilot submitted a piece of fabric from his flight suit, which had been sprayed with a fluid when the fire occurred, to the National Transportation Safety Board Material Laboratory. An ultraviolet lamp was used to visualize stains on the fabric; several spots were found. The most stained area was examined using a Fourier Transform Infrared spectrometer with a diamond attenuated total reflectance accessory. The spectrum contained a combination of spectral peaks corresponding to particular functional groups consistent with a phosphate ester. Phosphate esters are commonly found in hydraulic fluid. The presence amide was likely due to an additive to the hydraulic fluid. A spectral library search was performed using the residue spectrum. There were no exact matches to a hydraulic fluid, however, the unknown spectrum had several similarities to a few lubricating oils which are spectrally similar.

Post-accident examination of the airplane revealed the engine was separated from the airframe, and the propeller was separated from the engine. The propeller blades displayed features consistent with engine power. Fire consumed most the cockpit and the underlying systems between the firewall and aft cockpit. Due to the fire damage, the ignition and flammable sources could not be determined.

The T-28 flight manual Landing Gear System description stated that the landing gear is held up by mechanical locks. All the landing gear uplocks are released by initial movement of the landing gear handle; consequently, in event of hydraulic failure, the gear can be unlocked by the gear handle; the main gear extends by its own weight, and the nose gear is extended fully by a spring bungee.

The emergency checklist for Generator Failure stated that illumination of the generator-off warning light indicates that the generator is inoperative, and the battery is supplying all the power for the electrical system. In case of a generator failure:

Nonessential electrical equipment – OFF.

Conserve the battery by immediately turning off all nonessential electrical equipment. If necessary, place dc power switch at OFF and pull circuit breakers. 

Instrument power – NO. 1 INV.

(Unmodified aircraft – NO. 2 INV.) 

DC power – BAT ONLY (if radios and instruments are needed).

If flight can be conduced with instruments but without radios, place the dc power switch at BAT & GEN except when radios are required and before landing. 

The emergency checklist for Elimination of Smoke or Fuel Fumes was:

OXYGEN – 100% (if applicable).

Fuel pressure – CHECK.


If loss of fuel pressure is evident, refer to fuel pressure drop procedures.

Airspeed – Reduce immediately.

Reduce airspeed to minimize spreading and to minimize and to prepare for extraction*/bail-out if necessary.

Cockpit air – OPEN.

Air outlets – OPEN.

Windshield and canopy defrost – ON.


If smoke or fumes enter cockpit from any outlet, turn cockpit air handle to EMER OFF.

All nonessential electrical equipment – OFF.

Canopy – OPEN.

An open cockpit may aggravate a smoke of fuel fume condition. Open canopy, only a last resort.

Land at nearest suitable airfield.

The inflight emergency checklists for fire were: Engine Fire, Fuselage Fire, Wing Fire, and Electrical Fire. The Fuselage Fire checklist stated:

If fuselage fire occurs during flight, proceed as follows:

Check cause by shutting off the following, one at a time:

Cockpit heater – OFF.

Cockpit air – EMERG. OFF.

If fire continues, shutdown the engine and extract* or bail out.

If fire is extinguished, land at nearest suitable airfield.

The emergency checklist for Electrical Fire stated:

Circuit breakers isolate most electrical circuits and automatically interrupt power to prevent a fire when a short circuit occurs. However, if circuit breaker protection does not prevent an electrical fire, and if electrical power is essential (as during instrument flight), try to identify and isolate the defective circuit as follows:

Battery and generator – OFF.

All electrical equipment (except ignition) – OFF.

Battery and generator – Check operation separately.

Isolate defective equipment.

Turn on each circuit or piece of equipment individually and check load meter for abnormal reading. Allow sufficient time for the indication or reoccurrence of fire when restoring power to each circuit previously turned off.

Defective equipment switches – OFF.

Land nearest suitable airfield.

Following the accident, the pilot submitted the story of his accident flight to the North American Trainer Association publication, Skyline, and to Warbirds of America for publication. The story is included in the docket of this report. Several of the pilot's takeaways and suggestions, based on his perspective and experience of a fast onset of a very severe fire in the cockpit, were:

It is my suggestion that if you have generator failure in flight, or if you have any electrical component fail in flight, or if you sense that anything may be burning in the aircraft, switch all electrical power off immediate and land ASAP. In my case I don't know if the generator failure caused something electrical to short out or if something electrical shorted out and caused the generator to fail. As in my case, you never know what may be smoldering that can turn into a horrible fire. I made the very costly mistake of switching the power from battery/generator to battery only to maintain radio communication and also for landing gear and speed brake operation. Also, while I was only about 15 minutes from my home base, I passed three suitable airports in route. In my 38 years of flying, I have had generator failures many times and continued my flights to a preferred destination instead of landing at the first available airport.

Always fly high! - It gives one time to deal with emergencies and it also gives one the option to bail out in the event of a catastrophic fire. In my case, what appeared to be a simple generator failure resulted in a ferocious inflight fire in the cockpit. The fire was so intense that in the 20 to 25 seconds it took to fly the second half of the break to land, I was at the end of my human endurance and my burns were severe. Even being in the pattern at 1,000 feet, configured for landing and only 180 degrees of turn to go I could not complete the landing. I know it's very rare and impossible to predict if a generator failure will result in a ferocious fire. Regardless of the reason, if you have an in-flight fire you surely will want to exit the airplane ASAP. If you are cruising along at 180 knots with the airplane configured clean and you have a very fast onset of a ferocious fire you will not survive the time it takes to get the airplane on the ground with the fire burning. I would recommend being prepared ahead of time. 

First, if you have any suspicion that there may be an impending inflight fire, I recommend climbing to a bail out altitude and turning in the direction of a non-populated landscape. 

I would also recommend opening the canopy and dropping your speed brake, flaps and landing gear at altitude. When you activate these functions, you pressurize the hydraulic system. Better to find out if you're going to have a hydraulic system fire at altitude than in the pattern. If you do experience a ferocious fire, it is most likely driven by the engine driven fuel pump or the engine driven hydraulic pump. Also, as listed under emergency procedures, cut the engine fuel mixture immediately to stop the engine and stop feeding the blowtorch and also turn the fuel selector and electric fuel pump off.

Practice getting out of the aircraft with the parachute attached. - I often practiced getting out of my cockpit with my parachute attached in my hanger. Stepping up into the seat bucket with the parachute attached and staying out of the slip stream is harder than one realizes. 

I attribute my ability to get out of the burning cockpit with severe burns and compromised vision to my previous practice of getting out of the cockpit in the hangar with my parachute attached.

History of Flight

Sys/Comp malf/fail (non-power) (Defining event)

Fire/smoke (non-impact)
Loss of control in flight

Uncontrolled descent
Collision with terr/obj (non-CFIT)

Fire/smoke (post-impact) 

Pilot Information

Certificate: Private
Age: 65, Male
Airplane Rating(s): Multi-engine Land; Single-engine Land; Single-engine Sea
Seat Occupied: Front
Other Aircraft Rating(s): Helicopter
Restraint Used:
Instrument Rating(s): Airplane
Second Pilot Present: No
Instructor Rating(s): None
Toxicology Performed: No
Medical Certification: Class 2 With Waivers/Limitations
Last FAA Medical Exam: 07/12/2018
Occupational Pilot: No
Last Flight Review or Equivalent: 01/31/2018
Flight Time:  3500 hours (Total, all aircraft), 320 hours (Total, this make and model), 3500 hours (Pilot In Command, all aircraft), 0 hours (Last 90 days, all aircraft), 0 hours (Last 30 days, all aircraft), 0 hours (Last 24 hours, all aircraft)

Aircraft and Owner/Operator Information

Registration: N215SF
Model/Series: T-28B
Aircraft Category: Airplane
Year of Manufacture: 1955
Amateur Built:No 
Airworthiness Certificate: Other; Experimental
Serial Number: 137723
Landing Gear Type: Retractable -
Seats: 2
Date/Type of Last Inspection: 07/05/2018, Condition
Certified Max Gross Wt.: 8600 lbs
Time Since Last Inspection:
Engines: 1 Reciprocating
Airframe Total Time: 19426 Hours as of last inspection
Engine Manufacturer:Curtis Wright 
ELT: Installed
Engine Model/Series: R182086B
Rated Power: 1425 hp
Operator: Pilot
Operating Certificate(s) Held: None

Meteorological Information and Flight Plan

Conditions at Accident Site: Visual Conditions
Condition of Light:Day 
Observation Facility, Elevation: ANE, 912 ft msl
Distance from Accident Site: 0 Nautical Miles
Observation Time: 1108 CDT
Direction from Accident Site:
Lowest Cloud Condition: Clear
Visibility:  10 Miles
Lowest Ceiling: None
Visibility (RVR):
Wind Speed/Gusts: 10 knots /
Turbulence Type Forecast/Actual: None / None
Wind Direction: 180°
Turbulence Severity Forecast/Actual: N/A / N/A
Altimeter Setting: 30.02 inches Hg
Temperature/Dew Point: 25°C / 12°C
Precipitation and Obscuration: No Obscuration; No Precipitation
Departure Point:Blaine, MN (ANE) 
Type of Flight Plan Filed: None
Destination: Blaine, MN (ANE)
Type of Clearance: VFR
Departure Time: 1030 CDT
Type of Airspace: Class D

Airport Information

Airport: Anoka County-Blaine Airport (ANE)
Runway Surface Type:Asphalt 
Airport Elevation: 912 ft
Runway Surface Condition: Dry; Vegetation
Runway Used: 18
IFR Approach:None 
Runway Length/Width: 4855 ft / 100 ft
VFR Approach/Landing: Forced Landing; Traffic Pattern

Wreckage and Impact Information

Crew Injuries: 1 Serious
Aircraft Damage: Destroyed
Passenger Injuries: N/A
Aircraft Fire: In-Flight and On-Ground
Ground Injuries: N/A
Aircraft Explosion: None
Total Injuries: 1 Serious
Latitude, Longitude: 45.145000, -93.210278 (est)