NTSB Prelim: Beech F33 | Aero-News Network
Aero-News Network
RSS icon RSS feed
podcast icon MP3 podcast
Subscribe Aero-News e-mail Newsletter Subscribe

Airborne Unlimited -- Most Recent Daily Episodes

Episode Date

Airborne-Monday

Airborne-Tuesday

Airborne-Wednesday Airborne-Thursday

Airborne-Friday

Airborne On YouTube

Airborne-Unlimited-05.06.24

Airborne-NextGen-04.30.24

Airborne-Unlimited-05.01.24 Airborne-AffordableFlyers--05.02.24

Airborne-Unlimited-05.03.24

Mon, Mar 15, 2021

NTSB Prelim: Beech F33

The Pilot Announced That He Was Performing A Missed Approach

Location: Columbia, SC Accident Number: ERA21LA101
Date & Time: January 13, 2021, 10:33 Local Registration: N266DC
Aircraft: Beech F33 Injuries: 1 Fatal
Flight Conducted Under: Part 91: General aviation - Personal

On January 13, 2021 about 1033 eastern standard time, a Beech F33A, N266DC, was destroyed when it was involved in an accident near Columbia, South Carolina. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

Preliminary radar and air traffic control voice communication data provided by the Federal Aviation Administration indicated the airplane departed runway 19 at Greenville Downtown Airport (GMU) Greenville, South Carolina about 0959 under visual flight rules. At 1020, the pilot requested an instrument flight rules clearance while airborne and continued southeast toward Jim Hamilton L B Owens Airport (CUB), Columbia, South Carolina. The clearance was approved, and the airplane climbed to a cruise altitude of 5,300 ft and remained at that altitude until about 1007.

The pilot requested a pilot report (PIREP) from air traffic control about 1015, and the controller replied with a PIREP from 0930. About 1030, the controller advised the pilot of missed approach instructions, then at 1032 the pilot announced that he was performing a missed approach and requested the weather conditions at CUB.

Shortly after, radar contact with the flight was lost. The air traffic controller made several additional attempts to establish communications, but there were no further communications received from the pilot. About 0.3 nautical miles from runway 13 threshold, the airplane started a climbing left turn. While still turning left, the airplane then began to descend before radar contact was lost.

FMI: www.ntsb.gov

Advertisement

More News

ANN's Daily Aero-Term (05.02.24): Touchdown Zone Lighting

Touchdown Zone Lighting Two rows of transverse light bars located symmetrically about the runway centerline normally at 100 foot intervals. The basic system extends 3,000 feet alon>[...]

Aero-News: Quote of the Day (05.02.24)

“Discovery and innovation are central to our mission at Virgin Galactic. We’re excited to build on our successful record of facilitating scientific experiments in subor>[...]

Aero-News: Quote of the Day (05.03.24)

"We are reaching out to you today on behalf of the Popular Rotorcraft Association because we need your help. We are dangerously close to losing a critical resource that if lost, wi>[...]

ANN's Daily Aero-Term (05.03.24): UAS Traffic Management (UTM)

UAS Traffic Management (UTM) The unmanned aircraft traffic management ecosystem that will allow multiple low altitude BVLOS operations and which is separate from, but complementary>[...]

ANN's Daily Aero-Linx (05.03.24)

Aero Linx: Society of Aviation and Flight Educators (SAFE) SAFE is a member-oriented organization of aviation educators fostering professionalism and excellence in aviation through>[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

© 2007 - 2024 Web Development & Design by Pauli Systems, LC