Student Pilot Enters Controlled Airspace Without Authorization near Beja

Casualties unknown • Beja, PT

A student pilot operating a Socata TB 200 entered Beja controlled airspace without authorization, leading to an airspace violation incident.

What happened

On April 6, 2009, a SOCATA TB 200, registration CS-DEM, operated by the Academia Aeronáutica de Évora (AAE), departed Évora for a VFR navigation training flight. The flight plan, designated EVR 96, intended to fly via the "Echo" standard departure toward Reguengos de Monsaraz at a cruise altitude of 4,500 feet.

During the climb, the aircraft transitioned through 4,000 feet and established contact with Flight Information Service (FIS) on frequency 123.75 MHz. The FIS subsequently transferred the aircraft to Beja Approach (130.10 MHz). At 10:10 UTC, while stabilized at 4,500 feet, the pilot contacted Beja Approach. The military controller immediately notified the pilot that the aircraft had entered Working Area 03 without authorization. This specific area was being utilized by a military aircraft operating between FL060 and FL070. The controller instructed the pilot to descend to 2,000 feet and contact FIS. The pilot complied with the instructions, and the flight continued without further incident.

The investigation

The GPIAAF investigation focused on why the aircraft entered Class D controlled airspace without the necessary clearance. The investigation established that the aircraft entered a sector defined by radials R040-055, 20 DME, from the Beja VORTAC. The investigation examined the pilot's actions and the communication timeline between the aircraft and the FIS/Approach controllers.

Findings

  • The pilot failed to recognize the requirement to contact Beja Approach prior to entering the controlled airspace.
  • The student pilot lacked sufficient knowledge regarding the specific procedures required for operating within Class D airspace.
  • There was a delay in establishing communications between the aircraft and the FIS, which prevented the FIS controller from providing a timely warning to the pilot before the airspace violation occurred.
  • The primary cause was the pilot's failure to identify the need for authorization to enter controlled airspace.
  • There was no risk of mid-air collision during the event.

Probable cause

The incident was caused by the student pilot's failure to recognize the necessity of obtaining authorization before entering Class D controlled airspace, compounded by a lack of familiarity with Class D procedures and a delay in establishing radio contact with Flight Information Service.

Frequently asked questions

What happened in the 2009-04-06 Socata TB200 accident near Beja, PT?

A student pilot operating a Socata TB 200 entered Beja controlled airspace without authorization, leading to an airspace violation incident.

What aircraft was involved and where did it happen?

The accident on 2009-04-06 involved a Socata TB200, registration CS-DEM, at Beja, PT.

What was the probable cause of the accident?

The incident was caused by the student pilot's failure to recognize the necessity of obtaining authorization before entering Class D controlled airspace, compounded by a lack of familiarity with Class D procedures and a delay in establishing radio contact with Flight Information Service.

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 40,000+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.