Friday, August 28, 2020

Cessna 172S Skyhawk, N103VK: Accident occurred August 18, 2020 at Phoenix Deer Valley Airport (KDVT), Arizona

Federal Aviation Administration / Flight Standards District Office; Scottsdale, Arizona

Westwind School of Aeronautics LLC

https://registry.faa.gov/N103VK


NTSB Identification: WPR20CA293
14 CFR Part 91: General Aviation
Accident occurred Tuesday, August 18, 2020 in Phoenix, AZ
Aircraft: Cessna 172, registration: N103VK


NTSB investigators will use data provided by various entities, including, but not limited to, the Federal Aviation Administration and/or the operator, and will not travel in support of this investigation to prepare this aircraft accident report.

Aircraft made a hard landing damaging the firewall.

Date: 18-AUG-20
Time: 23:00:00Z
Regis#: N103VK
Aircraft Make: CESSNA
Aircraft Model: 172S
Event Type: ACCIDENT
Highest Injury: NONE
Aircraft Missing: No
Damage: SUBSTANTIAL
Activity: PERSONAL
Flight Phase: LANDING (LDG)
Operation: 91
City: PHOENIX
State: ARIZONA

Jewett SC-360, N36SC: Accident occurred August 27, 2020 at Van Aire Airport (CO12), Brighton, Adams County, Colorado

Federal Aviation Administration / Flight Standards District Office; Denver, Colorado

https://registry.faa.gov/N36SC



NTSB Identification: CEN20CA366
14 CFR Part 91: General Aviation
Accident occurred Thursday, August 27, 2020 in Brighton, CO
Aircraft: Backcountry Super Cubs SC-360, registration: N36SC

NTSB investigators will use data provided by various entities, including, but not limited to, the Federal Aviation Administration and/or the operator, and will not travel in support of this investigation to prepare this aircraft accident report.

Aircraft overturned on landing.

Date: 27-AUG-20
Time: 17:55:00Z
Regis#: N36SC
Aircraft Make: EXPERIMENTAL
Aircraft Model: SC-360
Event Type: ACCIDENT
Highest Injury: MINOR
Aircraft Missing: No
Damage: SUBSTANTIAL
Activity: PERSONAL
Flight Phase: LANDING (LDG)
Operation: 91
City: BRIGHTON
State: COLORADO

Van's RV-6A, N628JB: Accident occurred August 27, 2020 in Milton, Sussex County, Delaware

Federal Aviation Administration / Flight Standards District Office; Philadelphia

https://registry.faa.gov/N628JB


NTSB Identification: ERA20CA298
14 CFR Part 91: General Aviation
Accident occurred Thursday, August 27, 2020 in Milton, DE
Aircraft: Vans RV6, registration: N628JB


NTSB investigators will use data provided by various entities, including, but not limited to, the Federal Aviation Administration and/or the operator, and will not travel in support of this investigation to prepare this aircraft accident report.

Aircraft crashed in a field during a test flight.

Date: 27-AUG-20
Time: 18:00:00Z
Regis#: N628JB
Aircraft Make: VANS
Aircraft Model: RV6
Event Type: INCIDENT
Highest Injury: NONE
Aircraft Missing: No
Damage: UNKNOWN
Activity: PERSONAL
Flight Phase: MANEUVERING (MNV)
Operation: 91
City: MILTON
State: DELAWARE

Cessna 172P Skyhawk, N65645: August 27, 2020, May 18, 2018, April 12, 2017, July 02, 2016, and March 08, 2015

Federal Aviation Administration / Flight Standards District Office; South Florida

August 27, 2020: Aircraft had engine trouble and landed in swamp.

http://registry.faa.gov/N65645

Date: 27-AUG-20
Time: 16:45:00Z
Regis#: N65645
Aircraft Make: CESSNA
Aircraft Model: 172P
Event Type: ACCIDENT
Highest Injury: MINOR
Aircraft Missing: No
Damage: SUBSTANTIAL
Activity: INSTRUCTION
Flight Phase: MANEUVERING (MNV)
Operation: 91
City: HOLLYWOOD
State: FLORIDA





MIAMI (CBSMiami) – A single-engine aircraft ended up overturned in the Everglades, just west of Hollywood on Thursday afternoon.

Images from Chopper 4 showed two occupants standing on the plane’s wings awaiting rescue. They looked to be uninjured.

The Federal Aviation Administration identified the plane as a Cessna 172.

Officials said the aircraft was located 10 miles west of Hollywood and that it went down at around 12:45 p.m.

Rescuers had to get to the scene on airboats.

Here is what officials said about the rescue:

“When firefighters arrived, they met with two occupants, a pilot and a student whom were tucked underneath the tail section of the overturned Cessna which was miraculously still in one piece suffering only minor damage.”

“Both occupants were able to safely free themselves unassisted from the downed aircraft before rescue assets arrived. Both occupants are male, believed to be in their mid to late twenties suffering only minor injuries and were transported back to shore by airboat and then placed into a ground rescue for transport to Cleveland Clinic Hospital in Weston where they are expected to fully recover.”

The FAA is investigating, and the National Transportation Safety Board has been notified.

https://miami.cbslocal.com

Federal Aviation Administration / Flight Standards District Office; South Florida

May 18, 2018:  Aircraft landed in the grass east of runway.

Date: 18-MAY-18
Time: 15:40:00Z
Regis#: N65645
Aircraft Make: CESSNA
Aircraft Model: 172P
Event Type: INCIDENT
Highest Injury: NONE
Aircraft Missing: No
Damage: UNKNOWN
Activity: UNKNOWN
Flight Phase: LANDING (LDG)
Operation: 91
City: MIAMI
State: FLORIDA

Federal Aviation Administration / Flight Standards District Office; Orlando, Florida 

April 12, 2017:   Aircraft on landing, went off the runway.

Date: 12-APR-17
Time: 12:42:00Z
Regis#: N65645
Aircraft Make: CESSNA
Aircraft Model: C172
Event Type: INCIDENT
Highest Injury: NONE
Aircraft Missing: No
Damage: UNKNOWN
Activity: INSTRUCTION
Flight Phase: LANDING (LDG)
City: PEMBROKE PINES
State: FLORIDA



Federal Aviation Administration / Flight Standards District Office; Miami, Florida

Aviation Accident Final Report - National Transportation Safety Board: https://app.ntsb.gov/pdf

Docket And Docket Items - National Transportation Safety Board: https://dms.ntsb.gov/pubdms

NTSB Identification: GAA16CA360
14 CFR Part 91: General Aviation
Accident occurred Saturday, July 02, 2016 in Pembroke Pines, FL
Probable Cause Approval Date: 12/05/2016
Aircraft: CESSNA 172, registration: N65645
Injuries: 1 Uninjured.

NTSB investigators used data provided by various entities, including, but not limited to, the Federal Aviation Administration and/or the operator and did not travel in support of this investigation to prepare this aircraft accident report.

The student pilot reported that during the landing flare of his second solo, after the main landing gear touched down the "nose of the airplane swung" to the right. He further reported that he attempted to correct with left rudder, and that this is where "he lost control of the airplane". The airplane veered off the runway to the left, impacted an airport sign, and came to a stop at an intersecting taxi way. 

The airplane sustained substantial damage to the right wing. 

The student pilot did not report any mechanical malfunctions or failures with the airplane that would have precluded normal operation.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The student pilot's failure to maintain directional control during the landing flare, which resulted in a runway excursion, and impact with a sign.




Aviation Accident Final Report - National Transportation Safety Board: https://app.ntsb.gov/pdf

Docket And Docket Items - National Transportation Safety Board: https://dms.ntsb.gov/pubdms

NTSB Identification: ERA15CA153
14 CFR Part 91: General Aviation
Accident occurred Sunday, March 08, 2015 in Newport, RI
Probable Cause Approval Date: 08/11/2015
Aircraft: CESSNA 172P, registration: N65645
Injuries: 1 Uninjured.

NTSB investigators used data provided by various entities, including, but not limited to, the Federal Aviation Administration and/or the operator and did not travel in support of this investigation to prepare this aircraft accident report.

The student pilot was conducting a solo flight and landing on a 2,999-foot-long, 75-foot-wide, asphalt runway. During touchdown, the airplane began to bounce, and subsequently landed hard, which resulted in substantial damage to the nose landing gear and firewall. The airplane veered to the left and contacted a snowbank that extended parallel to the runway. The student pilot reported that he did not experience any preaccident malfunctions or failures that would have precluded normal operation. He further reported 43 hours of total flight experience, all in the same make model as the accident airplane, which included 7 hours logged as pilot-in-command.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The student pilot's failure to maintain aircraft control during landing, and his subsequent failure to recover from a bounced landing, which resulted in a hard landing.

Cessna 172R Skyhawk, N461CM: Incidents occurred September 30, 2020 and August 27, 2020

Federal Aviation Administration / Flight Standards District Office; Kansas City, Missouri 

September 30, 2020:  Aircraft hit a deer on landing at Higginsville Industrial Municipal Airport (KHIG), Lafayette County, Missouri.

University of Central Missouri

https://registry.faa.gov/N461CM

Date: 30-SEP-20
Time: 03:30:00Z
Regis#: N461CM
Aircraft Make: CESSNA
Aircraft Model: 172
Event Type: INCIDENT
Highest Injury: NONE
Aircraft Missing: No
Damage: UNKNOWN
Activity: PERSONAL
Flight Phase: LANDING (LDG)
Operation: 91
City: HIGGINSVILLE
State: MISSOURI

Federal Aviation Administration / Flight Standards District Office; Kansas City, Missouri

August 27, 2020: Aircraft experienced engine trouble and landed in a field, in Melbourne, Harrison County, Missouri.

Date: 27-AUG-20
Time: 18:30:00Z
Regis#: N461CM
Aircraft Make: CESSNA
Aircraft Model: R172
Event Type: INCIDENT
Highest Injury: NONE
Aircraft Missing: No
Damage: NONE
Activity: INSTRUCTION
Flight Phase: MANEUVERING (MNV)
Operation: 91
City: MELBOURNE
State: MISSOURI

Piper PA-28R-200 Arrow, N9341N: Accident occurred August 27, 2020 near Six Oaks Airport (NC67), Buncombe County, North Carolina

Federal Aviation Administration / Flight Standards District Office; Charlotte, North Carolina

Aircraft crashed shortly after departure in a corn field.


https://registry.faa.gov/N9341N


Date: 27-AUG-20

Time: 15:54:00Z
Regis#: N9341N
Aircraft Make: PIPER
Aircraft Model: PA28R
Event Type: ACCIDENT
Highest Injury: NONE
Aircraft Missing: No
Damage: SUBSTANTIAL
Activity: PERSONAL
Flight Phase: INITIAL CLIMB (ICL)
Operation: 91
City: ASHEVILLE
State: NORTH CAROLINA



BUNCOMBE COUNTY, North Carolina (WLOS) — A single-engine plane crashed in a Fairview cornfield shortly after taking off about noon Thursday.

Emergency crews on scene of plane 'accident' in Buncombe County

A woman said she saw the plane sputtering right before it went down.

"And as it got over the road, it started sputtering and kind of leaned to the right," Sioux Oliva said.

The plane went down off Lower Brush Creek Road near the Six Oaks Airport.

State Highway Patrol officials said 77-year-old Robert Vinroot and his passenger John McSpadden were trying to take off from a private airstrip when they crashed in a cornfield on the other side of Lower Brush Creek Road. The men had only minor scrapes.

https://wlos.com

Beechcraft A36 Bonanza, N1550G: Fatal accident occurred August 27, 2020 near Benton Field Airport (O85), Redding, Shasta County, California

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

Additional Participating Entity:
Federal Aviation Administration / Flight Standards District Office; Sacramento, California

Aviation Accident Preliminary Report - National Transportation Safety Board: https://app.ntsb.gov/pdf

https://registry.faa.gov/N1550G

Location: Redding, CA
Accident Number: WPR20LA289
Date & Time: 08/27/2020, 0630 PDT
Registration: N1550G
Aircraft: Beech A36
Injuries: 2 Fatal, 2 Serious
Flight Conducted Under: Part 91: General Aviation - Personal 

On August 27, 2020, about 0630 Pacific daylight time, a Beech A36, N1550G, was destroyed when it was involved in an accident near the Benton Field Airport (O85), Redding, California. The pilot and one passenger sustained fatal injuries, and two passengers sustained serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations 91 personal flight.

A witness, who was a rated pilot, located on O85, reported that the airplane was departing from runway 33, when it appeared to have "rotated too soon." The witness stated that the airplane became airborne briefly and immediately settled onto the runway before it became airborne a second time. The airplane subsequently touched down slightly beyond the departure end of the runway, crossed a road, and impacted trees, where a post impact fire ensued.

Examination of the accident site by local law enforcement revealed that the airplane came to rest down an embankment and was mostly consumed by fire. All major structural components of the airplane were located within the vicinity of the main wreckage. The wreckage was relocated to a secure location for further examination.

Aircraft and Owner/Operator Information

Aircraft Make:Beech 
Registration: N1550G
Model/Series: A36
Aircraft Category:Airplane 
Amateur Built: No
Operator: On file
Operating Certificate(s) Held: None

Meteorological Information and Flight Plan

Conditions at Accident Site: Visual Conditions
Condition of Light: Day
Observation Facility, Elevation: KRDD, 497 ft msl
Observation Time: 1353 UTC
Distance from Accident Site: 6 Nautical Miles
Temperature/Dew Point: 20°C / 15°C
Lowest Cloud Condition:
Wind Speed/Gusts, Direction: Calm / ,
Lowest Ceiling: Overcast / 3200 ft agl
Visibility:  4 Miles
Altimeter Setting: 29.79 inches Hg
Type of Flight Plan Filed: None
Departure Point: Redding, CA (O85)
Destination: Puyallup, WA (PLU) 

Wreckage and Impact Information

Crew Injuries: 1 Fatal
Aircraft Damage: Destroyed
Passenger Injuries: 1 Fatal, 2 Serious
Aircraft Fire: None
Ground Injuries: N/A
Aircraft Explosion:None 
Total Injuries: 2 Fatal, 2 Serious
Latitude, Longitude:  40.573611, -122.407222 (est)

Those who may have information that might be relevant to the National Transportation Safety Board investigation may contact them by email eyewitnessreport@ntsb.gov, and any friends and family who want to contact investigators about the accident should email assistance@ntsb.gov.

Mike Garrett



REDDING, California — Friends of the victim confirmed that Redding businessman, Mike Garrett, was one of the people killed in the plane crash that happened Thursday morning near the Benton Airpark.

Mike Garrett was a well-known member of Redding's business community and friends who spent time flying with him say he was an incredible person who had a big impact on the close-knit flying community.

Garrett was passionate about flying and it was a passion he shared with his pilot friends like Ron Lim of Redding

"[The] greatest person. Everybody loved Mike. There are so many friends and family here [in Redding] and at their house and a lot of support. And yeah... he's just a great guy. It's sad," Lim said. "He flew with me and loved it and went on to his license."

Lim described Garrett as a much-loved friend, father, and husband.

Garrett was the owner of Heavenly Donuts in Redding.

One other person in the plane died and two people were taken to the hospital.

https://krcrtv.com








A Beechcraft A36 Bonanza with four people onboard crashed Thursday morning in west Redding across from Benton Airpark, authorities said.

Two people onboard were killed and two were injured in the crash, Lt. Brian Cole of the Redding Police Department said. One of the people killed was identified late Thursday afternoon as Mike Garrett, owner of Heavenly Donuts in Redding.

“We initially got calls from citizens about a possible plane crash or explosion on the north side of Benton Airpark down into this hillside. There were four people on the plane, two of them were taken to Mercy Medical Center for significant injuries and we have two individuals that are deceased,” Cole said Thursday morning.

Cole said the four people onboard were adults.

"We have no knowledge of the gender at this point," he said. "The (Shasta County) Coroner’s office is doing a next-of-kin notification and then we’ll put out a press release later. But we won’t have that until the families have been notified.”

Federal Aviation Administration spokesman Ian Gregor said the plane crashed into a ravine around 6:45 a.m. after taking off from the airport.

Debra Fox, a close friend of the Garrett family, said Mike is survived by his wife, Katie, and sons Trevor and Nathan.

Authorities at this point do not know what caused the crash.

“We don’t have any information right now and I would imagine it would be awhile,” Cole said.

Firefighters put out a half-acre vegetation fire that started where the aircraft went down.

Neighbor Charlene Williams was inside her house on Placer Street when the crash happened.

"I was sitting on the couch and I heard this big crash and I had to run and put some clothes on because I wasn’t dressed yet and then I came out and I saw giant pillars of smoke and fire and everybody pulling up," Williams said.

Gregor said the FAA and the National Transportation Safety Board will be investigating the crash.

"The FAA will release the tail number of the aircraft after investigators verify it at the accident site," Gregor said.

The NTSB will not be going to Redding to investigate crash, rather the agency will work with local authorities to gather information, NTSB spokesman Terry Williams said.

"We understand there were several witnesses and we will be working on gathering statements from them," Williams said.

Placer Street was closed in both both directions at Pleasant Street and Airpark Drive but has since re-opened to one-way traffic each way, according to authorities.

The last major crash at Benton Airpark occurred nearly two years ago when a man and his dog were killed when his Cessna 150 crashed in a canyon just north of the airport.

The deadly crash happened on Aug. 29, 2018, after the plane had taken off on a Wednesday morning.

The pilot killed in the crash was later identified as Richard Joseph Engel, 71, of Shingletown.

https://www.redding.com

Cessna A185F Skywagon, N714KH and Piper PA-18-150 Super Cub, N7498L: Fatal accident occurred August 27, 2020 at Chena Marina Airport (AK28), Fairbanks, Alaska

Federal Aviation Administration / Flight Standards District Office; Fairbanks, Alaska

Aircraft involved in mid-air while landing.

Flying Moose Alaska LLC

https://registry.faa.gov/N714KH

Date: 27-AUG-20
Time: 22:20:00Z
Regis#: N714KH
Aircraft Make: CESSNA
Aircraft Model: A185
Event Type: ACCIDENT
Highest Injury: FATAL
Aircraft Missing: No
Damage: SUBSTANTIAL
Activity: ON DEMAND
Flight Phase: LANDING (LDG)
Operation: 135
Aircraft Operator:FLYING MOOSE ALASKA
City: FAIRBANKS
State: ALASKA

Involved in mid-air with Cessna A185F Skywagon, N714KH, while taking off.

https://registry.faa.gov/N7498L

Date: 27-AUG-20
Time: 22:20:00Z
Regis#: N7498L
Aircraft Make: PIPER
Aircraft Model: PA-18
Event Type: ACCIDENT
Highest Injury: SERIOUS
Aircraft Missing: No
Damage: SUBSTANTIAL
Activity: PERSONAL
Flight Phase: TAKEOFF (TOF)
Operation: 91
City: FAIRBANKS
State: ALASKA

Those who may have information that might be relevant to the National Transportation Safety Board investigation may contact them by email eyewitnessreport@ntsb.gov, and any friends and family who want to contact investigators about the accident should email assistance@ntsb.gov.







State of Alaska Department of Public Safety

Any charges reported in these press releases are merely accusations and the defendants are presumed innocent unless and until proven guilty.

AK20060097
Location: Fairbanks
Type: Aircraft Collision- Fatal
Dispatch Text:

UPDATE:

AST has positively identified the other two occupants of the Cessna 185. Cody J. Rosania (35 yoa of Buckeye, AZ) died in the crash. Rayne R. Rush (40 yoa of Buckeye Arizona) was the third occupant inside the C185, he suffered life-threatening injuries. Family members have been notified. The State Medical Examiner's Office called for an autopsy of both men who died.

On 8/27/20 at 1355 hours AST received a report of a mid-air collision above the airstrip which is parallel to Dolphin Way in west Fairbanks. AST, AWT, Airport Police & Fire Department and Chena Goldstream Fire & Rescue responded to the scene. Initial investigation indicated a Piper Supercub flown by Larry D. Dalrymple (73 yoa of Fairbanks) collided with a Cessna 185 (corrected model) flown by Shane E. Bennett (52 yoa of Fairbanks). After the collision both aircraft crashed into the ground on the gravel runway. The Cessna 185 burst into flames on impact. Dalrymple was seriously injured and he was transported to FMH. Bennett was killed in the crash. A 40 yoa male was extricated from the burning wreckage and was transported to FMH with life-threatening injuries. One other passenger was inside the C185 and that person was also killed in the crash. AST has not been able to notify next of kin for the second deceased person. The critically injured person has been identified, but AST has not notified the next of kin yet. AST notified NTSB of the crash. Local FAA personnel are on scene and they are investigating the crash. The airfield is currently closed for an indefinite amount of time. AWT and AST are still on scene assisting with scene security.

Posted on 8/27/2020 3:49:49 PM by DPS\bjwassmann

https://dailydispatch.dps.alaska.gov

Loss of Control in Flight: Beechcraft 58 Baron, N501CE; fatal accident occurred April 22, 2019 near Kerrville Municipal Airport (KERV), Kerr County, Texas

(clockwise from upper left) Jeffrey Weiss, Angela & Stuart Kensinger, Mark Scioneaux, Marc Tellepsen and Scott Reagan Miller.

The National Transportation Safety Board traveled to the scene of this accident.

Additional Participating Entities:

Federal Aviation Administration / Flight Standards District Office; San Antonio, Texas
Continental Aerospace Technologies; Mobile, Alabama
Textron Aviation Inc; Wichita, Kansas

Aviation Accident Final Report - National Transportation Safety Board: https://app.ntsb.gov/pdf


Investigation Docket - National Transportation Safety Board: https://dms.ntsb.gov/pubdms


https://registry.faa.gov/N501CE

Location: Kerrville, TX
Accident Number: CEN19FA124
Date & Time: 04/22/2019, 0851 CDT
Registration: N501CE
Aircraft: Beech 58
Aircraft Damage: Substantial
Defining Event: Loss of control in flight
Injuries: 6 Fatal
Flight Conducted Under: Part 91: General Aviation - Business

Analysis 

The pilot was conducting an instrument flight rules (IFR) flight in a twin-engine airplane with five passengers. During a GPS approach to the destination airport, both engines lost total power within 10 seconds of each other; the left engine regained near full power about 40 seconds later, which it maintained until the end of recorded data. As the pilot continued the approach, he did not ensure the flaps were up or feather the propeller of the inoperative right engine, which was contrary to the airplane manufacturer's emergency procedures guidance.

As the airplane descended with the right engine inoperative below the cloud ceiling to about 500 ft agl, its flightpath leveled and airspeed decreased below the minimum controllable airspeed (Vmc). The airplane's continued flight profile below Vmc with the unfeathered propeller of the inoperative right engine, the left engine near full power, and the airplane's aft center of gravity resulted in a right-turning spin and ground impact.

The pilot's filed flight plan indicated a minimum fuel load required of 58 gallons, although this did not account for the instrument approach and alternate airports. However, the pilot's flight planning log indicated only 50 or 54 gallons of fuel onboard. Thus, based solely on the pilot's logs, there was insufficient fuel onboard the airplane to embark on the flight. Because the airplane was beyond its maximum gross weight with just 50 gallons of fuel onboard, it is likely that the pilot did not want to add additional fuel. Thus, the pilot's decision to depart on the accident flight without adequate fuel onboard showed poor judgement.

Although the pilot departed without an adequate fuel reserve for the IFR flight, an actual fuel load of 50 or 54 gallons would have been sufficient to reach the destination airport (the airplane burned about 42 gallons just before the crash site about 6 miles from the airport). However, when the airplane was fueled at the pilot's request 8 days (five flights) before the accident flight, it was not completely filled. Because the pilot was not present for the fueling and did not crosscheck the fuel receipt with his fuel-planning logs, he did not recognize that the error meant he had less than 50 gallons of fuel onboard before departing on the accident flight. As evidenced by the close correlation between the pilot's fuel logs and the engine data monitoring (EDM) fuel consumption data for the accident flight and the five flights before it, the pilot mainly relied on EDM data to determine the quantity of fuel onboard the airplane. Thus, the fueling error introduced 8 days before the accident was carried through the pilot's planning logs for the next six flights, including the accident flight.

Further review of the accident airplane fueling records, the pilot's flight-planning logs, and fuel consumption data from the EDM revealed that the airplane actually had about 12 gallons less fuel than the pilot indicated in his fuel log for the accident flight. Thus, the lack of sufficient fuel for the accident flight resulted in the airplane's engine power loss during the approach.

In addition, the abnormally high resistances in both fuel quantity transmitters would have caused the cockpit fuel quantity indicators for both wings to read about 5 gallons higher each than the actual fuel present, corresponding to an additional 1/16th tank on each of the indicators. Thus, because of the high resistances in both fuel quantity transmitters, the pilot's belief that 50 (or 54) gallons of fuel were onboard at takeoff (rather than the actual fuel level of 38 gallons) may have been corroborated by the fuel quantity indicators; however, the effect of the inaccurate indications on the pilot's actions are uncertain.

The pilot's autopsy indicated he had severe coronary artery disease, which placed him at increased risk of a sudden cardiac event. However, the accident sequence was not consistent with acute pilot impairment or incapacitation as recorded data indicate that the pilot was controlling the airplane up until the airplane dropped below its minimum controllable airspeed, so it is unlikely that the pilot's coronary artery disease or any sudden medical event contributed to this accident.

In summary, multiple errors before takeoff led to a loss of engine power due to fuel exhaustion. The pilot did not accurately record the amount of fuel added after fueling, the pilot did not verify the amount of fuel onboard the airplane, the fuel quantity transmitters did not accurately indicate the amount of fuel onboard, and the pilot decided to take off with inadequate fuel to conduct the IFR flight in an overweight airplane. Lastly, during the flight, once the right engine lost power, the pilot failed to properly configure the airplane per the manufacturer's emergency procedures guidance and allowed the airspeed to drop below the point at which the airplane could maintain flight. 

Probable Cause and Findings

The National Transportation Safety Board determines the probable cause(s) of this accident to be:
The pilot's inadequate preflight fuel planning and fuel management, which resulted in a loss of engine power due to fuel exhaustion. Also causal was the pilot's failure to follow the one-engine inoperative checklist and maintain the airplane's minimum controllable airspeed by properly configuring the airplane, which resulted in a loss of airplane controllability. 

Findings

Aircraft
Fuel - Fluid management (Cause)
Fuel - Fluid level (Cause)
Airspeed - Not attained/maintained (Cause)
Performance/control parameters - Not attained/maintained (Cause)
Fuel quantity indicator - Damaged/degraded
Maximum weight - Capability exceeded

Personnel issues
Fuel planning - Pilot (Cause)
Decision making/judgment - Pilot (Cause)
Use of checklist - Pilot (Cause)
Aircraft control - Pilot (Cause)
Flight planning/navigation - Pilot
Weight/balance calculations - Pilot

Factual Information

History of Flight

Approach
Fuel exhaustion

Approach-IFR final approach
Loss of control in flight (Defining event)

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

On April 22, 2019, at 0851 central daylight time, a Beech 58 airplane, N501CE, was substantially damaged when it was involved in an accident near Kerrville Municipal Airport (ERV), Kerrville, Texas. The pilot and five passengers died. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 business flight.

According to airport surveillance video from West Houston Airport (IWS), Houston, Texas, the pilot accomplished an abbreviated preflight inspection of the airplane, during which he appeared to visually check the exterior left-wing fuel level sight gauge but not the right-wing fuel level sight gauge; the pilot did not sump any of the 10 fuel drains. The pilot returned to the terminal to meet the passengers, and after both engines were started, the airplane departed about 0730.

According to air traffic control (ATC) and automatic dependent surveillance-broadcast (ADS-B) information, after departing IWS, the pilot obtained an instrument flight rules (IFR) clearance and was instructed to climb to 3,000 ft mean sea level (msl). The flight proceeded toward ERV, climbing to a cruise altitude of 6,000 ft msl. About 0824, the pilot requested the RNAV (GPS) instrument approach for runway 12 and was cleared for the approach via a procedure turn and to descend to 4,000 ft. About 0833, the pilot reported his descent to 4,000 ft and the controller advised that "bases were 2,400," which the pilot acknowledged.

About 0839, the pilot was cleared for the GPS instrument approach to runway 12 and instructed to maintain 4,000 ft to the initial fix for the approach (OBUCO) (see figure 1). Once the airplane was in-bound to the airport, about 0843, the controller directed the pilot to switch to the ERV advisory frequency, which was unmonitored. The GPS instrument approach profile for runway 12 included a descent to 3,300 ft msl at 5.3 nautical miles from the runway.

Figure 1. A Google Earth aerial view of terrain near the accident site with overlaid ADS-B data and approach information.

According to ADS-B data, the airplane maintained an altitude of 3,900 ft until about 0844:59, when it began a steady descent; the airplane was about 13 miles from the runway. Data from the airplane's engine data monitor (EDM) indicate that the left engine lost power about 0845 followed by the right engine about 10 seconds later. ADS-B data indicated that the airplane steadily descended well below the approach profile.

EDM data indicated that, about 40 seconds after losing power, the left engine regained near full power, which it maintained until the end of recorded EDM data about 0851. ADS-B data indicated that the airplane slowed below the minimum controllable airspeed (Vmc) of 83 knots as it descended from about 500 to 300 ft agl, and the descent rate decreased. A witness on the ground saw the airplane on final approach at a low altitude, when it entered a right turn, began a right spiral, and disappeared behind a ridge line. 

Pilot Information

Certificate: Airline Transport; Private
Age: 65, Male
Airplane Rating(s): Multi-engine Land; Single-engine Land; Single-engine Sea
Seat Occupied: Left
Other Aircraft Rating(s): None
Restraint Used: 3-point
Instrument Rating(s): Airplane
Second Pilot Present: No
Instructor Rating(s): None
Toxicology Performed: Yes
Medical Certification: Class 2 With Waivers/Limitations
Last FAA Medical Exam: 10/10/2018
Occupational Pilot: No
Last Flight Review or Equivalent: 11/01/2018
Flight Time:  (Estimated) 5671 hours (Total, all aircraft), 2409 hours (Total, this make and model), 5565 hours (Pilot In Command, all aircraft), 106 hours (Last 90 days, all aircraft), 59 hours (Last 30 days, all aircraft), 1 hours (Last 24 hours, all aircraft) 

A flight instructor who frequently flew with the pilot and conducted his most recent flight review stated the pilot's mechanical flying skills were very good but, on occasion, his understanding of technical issues was not as strong. The flight instructor noticed a few times when the pilot did not perform well during unexpected in-flight issues. He stated the pilot normally planned to land with at least 1 hour of fuel remaining.

Aircraft and Owner/Operator Information

Aircraft Make: Beech
Registration: N501CE
Model/Series: 58
Aircraft Category: Airplane
Year of Manufacture:
Amateur Built: No
Airworthiness Certificate: Normal
Serial Number: TH-1888
Landing Gear Type: Retractable -
Seats: 6
Date/Type of Last Inspection: 08/27/2018, Annual
Certified Max Gross Wt.: 5500 lbs
Time Since Last Inspection: 105 Hours
Engines: 2 Reciprocating
Airframe Total Time: 3834 Hours at time of accident
Engine Manufacturer: Continental
ELT: C91A installed, not activated
Engine Model/Series: IO-550C
Registered Owner: On file
Rated Power: 300 hp
Operator: On file
Operating Certificate(s) Held: None

Fuel System

The airplane's fuel system comprised three fuel cells and one wet tip tank for each wing. Total fuel capacity for the airplane was 200 gallons; the three fuel cells in each wing held a total of 83 gallons of usable fuel and 3 gallons of unusable fuel, and the wet tip tank held 14 gallons of fuel, all of which was usable.

The wing fuel cells and wet tip tanks were interconnected so that all usable fuel was available with the fuel selector valve for each wing in the ON position and supplying fuel to its respective engine. The CROSSFEED position on the fuel selector was only to be used in an emergency. Each wing had two flush-type fuel filler caps: one located in the outboard end of each outboard leading-edge fuel cell and one in the wet tip fuel tank.

Fuel quantity was measured by float-type units that electrically transmitted a single indication for each wing system to fuel quantity indicators in the cockpit. The fuel quantity indicator would show full until the respective wing fuel cells contained less than about 75 gallons. According to an American Bonanza Society (ABS) technical representative, the three fuel quantity transmitters in each wing were wired in series with one another. Fuel quantity would be at least 75 gallons at 199 ohms and 3 gallons of unusable fuel at 0 ohms. In this range, the resistance value of the transmitter circuits in each wing was designed to be directly proportional to the amount of fuel.

The caution range (yellow band) on the cockpit fuel quantity indicators was from 0 to 1/8th of the amount indicated by the fuel quantity indicator (about 9.33 gallons usable per wing).

Fuel level sight gauges on the leading edge of each wing only indicated fuel levels from 40 to 60 gallons per wing. It was not possible to use a dipstick to check fuel quantity due to each wing's dihedral and the location of the filler caps.

Fueling Information

Fueling of an exemplar 1999 Beech 58 showed that when the airplane's wing fuel cells were filled as much as possible from the inboard wing filler caps, the wet tip tanks became partially filled because of the wing's dihedral, resulting in a total of 188 gallons of fuel (182 usable) on board. In order to fill the wet tip tanks, about 6 gallons of fuel would be added to each tip tank through the wet tip tank fuel filler cap.

Fuel Consumption

The accident airplane's EDM indicated that the airplane consumed about 28 gallons of fuel per hour (gph) during the accident flight while at cruise power. According to the airplane's pilot operating handbook (POH), the airplane consumed about 34 gph of fuel at maximum cruise power (200 kts) and about 18 gph at economy cruise power (163 kts).

Weight and Balance

The airplane's maximum gross weight was 5,500 lbs. Based on passenger weights provided by the medical examiner, the airplane's takeoff weight was calculated as 5,598 lbs with 50 gallons of usable fuel and 5,526 lbs with 38 gallons of usable fuel. The airplane's center of gravity was 86.7 inches at the time of the accident; the acceptable cg range with low fuel was 77.7 to 86.2 inches.

Airplane Performance

The Beech 58 engine-out procedure in the POH directed flaps to be retracted and the propeller of the inoperative engine to be feathered. The airplane's performance charts indicated a one-engine-inoperative climb capability of about 300 feet per minute (fpm) with the inoperative engine's propeller feathered, flaps up, and a gross weight of 5,300 lbs.

A flight operations pilot for the airplane manufacturer who regularly performed single-engine drag demonstrations reported that lowering flaps from 0° to 15° with one engine inoperative resulted in a 150-fpm decrease in climb rate and an unfeathered propeller configuration resulted in a 400-fpm decrease in climb rate.

Meteorological Information and Flight Plan

Conditions at Accident Site: Instrument Conditions
Condition of Light: Day
Observation Facility, Elevation: KERV, 1617 ft msl
Distance from Accident Site: 6 Nautical Miles
Observation Time: 0855 CDT
Direction from Accident Site: 121°
Lowest Cloud Condition:
Visibility:  10 Miles
Lowest Ceiling: Overcast / 1200 ft agl
Visibility (RVR):
Wind Speed/Gusts: 11 knots / 17 knots
Turbulence Type Forecast/Actual: None / None
Wind Direction: 170°
Turbulence Severity Forecast/Actual: N/A / N/A
Altimeter Setting: 30.04 inches Hg
Temperature/Dew Point: 18°C / 16°C
Precipitation and Obscuration: No Obscuration; No Precipitation
Departure Point: Houston, TX (IWS)
Type of Flight Plan Filed: IFR
Destination: Kerrville, TX (ERV)
Type of Clearance: IFR
Departure Time: 0729 CDT
Type of Airspace: Class E 

The 1,200 ft agl ceiling reported by the ERV automated weather observation system correlated to a ceiling at the accident site of about 950 ft agl. A pilot who flew an approach to ERV reported 2,400 ft msl cloud bases, which correlated to a ceiling at the accident site of about 550 ft agl. 

Airport Information

Airport: Kerrville Muni/Louis Schreiner (ERV)
Runway Surface Type: Asphalt
Airport Elevation: 1616 ft
Runway Surface Condition: Dry
Runway Used: 12
IFR Approach: Global Positioning System; RNAV
Runway Length/Width: 6004 ft / 100 ft
VFR Approach/Landing: Full Stop 

Wreckage and Impact Information

Crew Injuries: 1 Fatal
Aircraft Damage: Substantial
Passenger Injuries: 5 Fatal
Aircraft Fire: None
Ground Injuries: N/A
Aircraft Explosion: None
Total Injuries: 6 Fatal
Latitude, Longitude: 30.037500, -99.185833

The airplane impacted a rocky ravine about 120 yards from the final radar data point and about 6 miles from the airport. There was no postimpact fire and the airplane came to rest upright on a heading of 246° (see figure 2). The wreckage was contained within the footprint of the airplane, indicating a low forward groundspeed. Elevation at the accident site was 1,868 ft msl and trees about 40 yards northeast were the nearest obstructions.

Figure 2. Photograph of an aerial view of the accident site

All flight control surfaces were present and flight control cable continuity was established from the tail surfaces to the aft empennage, where the cables were bound by the cabin floor, which was crushed by impact forces. Aileron and aileron trim tab cable continuity was established from the control surface to the wing root.

About 1 gallon of fuel was drained from the left-wing fuel cells on the day of the accident. When the left wing was lifted at the wing tip on the day after the accident, about 1 cup of fuel was observed in the left-wing fuel cells and about 1 cup of fuel drained from a breached area near the engine nacelle. No fuel was observed in the right-wing wet tip tank or the right-wing fuel cells. All fuel tank caps were secured. There was no evidence of fuel blight on the area surrounding the airplane.

Four of the six fuel cells were in their installed position with no obstructions. The left-wing box cell was loose at the top due to impact damage and the right-wing inboard leading-edge fuel cell was in the installed position, except where cut by recovery personnel.

The left fuel selector was near the ON position; it was positioned about 1/4 toward OFF. A small amount of fuel was found in the left fuel selector valve and fuel strainer. The right fuel selector was in the ON position. No fuel was present in the right fuel selector valve or fuel strainer. No water was detected.

Postaccident resistance testing of the six fuel quantity transmitters revealed a total transmitter resistance at the empty setting of 13.7 ohms in the left wing and 14.6 ohms in the right wing. Factory specification resistance for each of the six individual transmitters was 0 to 0.5 ohm at the empty setting.

According to the ABS technical representative, the additional resistance found in the six transmitters corresponded to a reading of about 5 gallons more than the actual fuel for each wing, (or about 1/16 tank more than the actual amount shown on each fuel quantity indicator), which would equal about 20 to 24 minutes of flying time. Impact damage precluded testing for additional resistance in the fuel quantity circuits.

Both fuel quantity gauges and engine fuel flow transducers were tested, with no anomalies noted. Testing reports are in the docket for this investigation.

The landing gear were in a retracted position. The left-wing flap actuator position corresponded to a 15° flap setting; the right-wing flap actuator was fractured. Both electric fuel boost pump switches were at the high position. The throttle, propeller, and mixture controls were all near the full-forward position.

The propeller for the left engine separated from the engine during the impact sequence. Blades 'A' and 'B' remained attached to the hub. Blade 'A' exhibited leading-edge burnishing and was bent aft at the tip. Blade 'B' exhibited leading-edge gouging, chordwise and spanwise scratching, and was curled forward from the root. Blade 'C' was located under the left-engine cowling and curled aft at the tip with gouging.

The propeller for the right engine remained attached to the engine and all three blades remained in the hub. Blade 'A' was straight with minimal damage. blade 'B' was bent aft at the root, and blade 'C' was straight, with light leading-edge gouging along the outer half of the blade. The position of the three blades was not feathered and was in or near the low-pitch stop position.

Both engines were examined, and no engine anomalies were observed that would have prevented normal operation. 

Medical And Pathological Information

An autopsy of the pilot was performed at the Travis County Medical Examiner's Office, Austin, Texas. The cause of death was blunt force injuries. The autopsy found atherosclerotic arterial disease, including greater than 90% stenosis of the right coronary artery, greater than 90% stenosis of the left anterior descending coronary artery, 60% to 70% stenosis of the left main coronary artery, 40% to 50% stenosis of the left circumflex coronary artery, and 20% to 30% stenoses of the right and left coronary ostia (all percentages approximate). The autopsy found no other significant natural disease.

Toxicology testing of the pilot's tissue and fluid samples performed at the Federal Aviation Administration (FAA) Forensic Sciences Laboratory detected naproxen, fexofenadine, azacyclonol, rosuvastatin, and irbesartan in blood and urine. These drugs are not considered impairing.

According to the pilot's girlfriend, the pilot was well rested and in good health, both mentally and physically, before the accident flight. Airport surveillance video showed that the pilot appeared to be alert during the hour before the flight. 

Additional Information

EDM Data

A J.P. Instruments EDM-760 was recovered from the wreckage and downloaded. Data from the last 10 flights, including the accident flight, were recorded at 6-second intervals; these data included fuel flow, fuel used, exhaust gas temperatures, cylinder head temperatures, and shock cooling rate of the two engines.

After fuel flow to the left engine decreased to 0 gph where it remained for about 40 seconds, fuel flow increased to about 32 gph and remained near 30 gph for the remainder of the recorded data. After fuel flow to the right engine decreased to 0 gph, it remained near 0 until about 4 minutes before the end of the data, when it increased to about 15 gph for a few seconds and then returned to 0. About 3 minutes before the end of the data, the right engine fuel flow rose to between 2 and 6 gph for about 30 seconds and then returned to 0, where it remained for the remainder of the recorded data.

Total fuel used on the accident flight was about 42 gallons, with the left and right engines consuming 22 and 20 gallons, respectively. Based on the left engine restarting and running at 30 gph for about 6 minutes, the total fuel used at the time of the power loss of both engines was about 39 gallons.

Total fuel used between the fueling on April 14 and the accident flight, was 214.7 gallons, with the left and right engines consuming 108 and 106.7 gallons, respectively.

Performance Study

As stated above, the wreckage examination found that the flaps were positioned at 15° and the right engine propeller was not feathered. The NTSB's performance study found that had the pilot feathered the propeller of the inoperative right engine and retracted the flaps, the resulting reduction in drag would have been sufficient to maintain the airplane's glideslope to the runway assuming that the left engine maintained thrust.

Fuel Planning

For IFR flight plans, 14 CFR 91.167 requires enough fuel to reach the destination airport and an alternate airport, plus 45 minutes of flight time at normal cruising speed.

Before departure, the pilot planned several routes from IWS to ERV using the ForeFlight mobile flight-planning application. The pilot checked airport information at ERV and two airports between IWS and ERV (the airports were closer to IWS than ERV). He did not check information for alternate airports in the vicinity of ERV.

The pilot filed an IFR flight plan using flightplan.com, which included a navigation log that provided fuel calculations based on information entered by the pilot. Estimated fuel consumption for the flight was about 38 gallons, which included 5 gallons of taxi fuel; the navigation log included fuel required for the IFR flight of about 58 gallons, including a 45-minute fuel reserve at normal cruising speed of 20.3 gallons. The navigation log did not include fuel for an instrument approach at ERV, and an alternate airport was not designated. Postaccident calculations of the fuel required for the IFR flight indicated that a minimum of 67 gallons would be required, which included fuel for an instrument approach to ERV, 6 gallons of fuel for an instrument approach at the closest alternate airport, and 20 gallons of reserve fuel.

Flight Planning Log

The pilot used a flight-planning log to record starting and ending fuel for each flight. The log showed the date, departure and landing locations, the tachometer start and stop times, the total flight time, and the beginning and ending fuel (in gallons) for each flight. The pilot likely based the fuel consumption information on the EDM data. Figure 3 shows the six previous flights, beginning on April 14, as well as the accident flight.


Figure 3. Pilot's Flight-Planning Logs

According to the fueling company manager at IWS, the pilot would typically order fuel over the telephone and would not be present when the airplane was fueled. The pilot's normal fuel order was to fill only the wing fuel cells (not the wet tip tanks). The pilot's fuel order 8 days before the accident (on April 14) was taken over the phone and transcribed on a service request form as "T/O x 4." In postaccident interviews, the fueler stated that he understood the order as written to be a "top off" of the wing fuel cells and wet tip tanks for both wings and recalled fueling the airplane until the main fuel cells and wet tip tanks were completely full. The fuel receipt from the IWS fueling company on the evening of April 14 indicated that 113 gallons of fuel were added.

Before the fueling on April 14, the pilot's fuel log indicated an ending fuel of 60 gallons (see the top of figure 3). As shown in figure 3, the pilot recorded 194 gallons as the starting fuel for the first flight on April 15. However, based on the fuel quantity indicated on the fuel receipt, the total fuel should have been recorded as 173 gallons (60 gallons on the fuel log plus the 113 gallons on the fuel receipt); thus, the pilot's fuel log indicated a starting fuel load 21 gallons more than it should have been on April 15.

The log indicated that the ending fuel for the flight before the accident flight, on April 17, was 50 gallons; however, it appears that the pilot wrote 54 as the beginning fuel for the accident flight (highlighted at bottom of figure 3). The investigation was unable to determine the reason for this difference given that no fuel order or fuel receipt for the period between April 17 and the day of the accident was located, and the fueling company at IWS does not offer a self-service fueling option.

Given the noted errors above, the investigation used the EDM fuel consumption data to determine how much fuel was actually onboard the airplane after the 113 gallons were added on April 14. Based on the confirmed fueling of 30 gallons on April 17 and the EDM fuel consumption data for the flights between April 14 and the accident, the investigation determined that usable starting fuel on April 15 was about 182 gallons, which was 12 gallons less than the amount the pilot recorded.

Spin Avoidance and Recovery Guidance

In March 2006, Raytheon Aircraft Corporation (RAC) issued Safety Communiqué No. 249, "Spin Avoidance and Spin Recovery Characteristics," which includes the following information:

A spin can occur whenever an airplane is stalled and is subject to yaw input. Yaw input can be provided by rudder, asymmetric power, aileron, p-factor, or any combination of these forces. Any time asymmetric power is allowed to continue through spin entry and into a developed spin, a dangerous and possible unrecoverable spin (to the left or right) could be encountered.

According to the FAA Airplane Flying Handbook:

No multi-engine airplane is certified for spins, and their spin characteristic is generally poor. As very few twins have been spin tested (none are required to), the recommended spin recovery techniques are based only on the best information available. The departure from controlled flight may be quite abrupt and possibly disorienting.

FAA Advisory Circular 61-67C, "Stall and Spin Awareness Training," includes the follow information:

The center of gravity has a significant effect on stability and stall/spin recovery. As the center of gravity is moved aft, the amount of elevator deflection needed to stall the airplane at a given load factor will be reduced. An increased angle of attack will be achieved with less elevator control force. This could make the entry into inadvertent stalls easier, and during the subsequent recovery, it would be easier to generate higher load factors due to the reduced elevator control forces.

Although the hilly, rocky, and wooded terrain near the accident site offered limited forced landing options, a plateau with a dirt road was in front of the airplane before the right turn at the end of the flight.

American Bonanza Society Article

After the accident, the June 2019 issue of American Bonanza Society Magazine published an article reminding pilots of prudent actions when refueling and noting the following:

Whenever possible, personally fuel your airplane, or watch it being refueled. Ensure that the proper type and quantity of fuel is added in the tanks you want it put into. Compare the fuel bill to your expectations. Check the amount of fuel that was added against the amount you thought you would need. If there is a big discrepancy, figure it out, whether less fuel than you expected was put in or you needed more than you thought because your fuel tracking was flawed on prior flights.

Ensure your fuel gauges are accurate. Our Australian friends are required to have their fuel gauges calibrated .... and a placard next to the gauges that show the instrument error for each marking on the gauges, similar in concept to a compass correction card. It is possible for our fuel gauges to be reliable.

Fuel Quantity System Maintenance Guidance

The Beech 58 annual inspection guide specified checking "for proper operation and unusual fluctuations" of fuel quantity gauges. The Beech maintenance manual recommended fuel quantity transmitters be overhauled or replaced as necessary.

In general, no FAA regulations and little guidance addressed periodically checking the accuracy of fuel quantity indicators. In response to a reported safety concern, a 2003 special airworthiness information bulletin (SAIB) recommended owners of Cessna 100, 200, 300, and 400 airplanes perform calibration checks of both the empty and full positions of their airplanes' gauging system at the next inspection then at 5-year intervals.


The NTSB is aware that, based on this accident and other fuel-related accidents involving resistance-type fuel quantity gauging systems, the FAA is working on an SAIB addressing all aircraft with such systems.












Kerr County Sheriff Rusty Hierholzer walks along Sheppard Rees Road, near the location where a Beechcraft 58 Baron crashed just outside Kerrville on private land, on April 22, 2019.


Kerr County Sheriff Rusty Hierholzer, center, makes a phone call, April 22, 2019, where his deputies guard the entrance to a private road near Kerrville, Texas, where a  Beechcraft 58 Baron crashed earlier in the day, killing all six people onboard.


Local resident and former pilot Robert Hurt said he was puzzled why the plane was so far out on its final approach to the airport. He said weather conditions were good.
Construction worker Richard Hall describes the last moments of before a Beechcraft 58 Baron crashed near Kerrville. He said plane flew over his work site.