FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR23FA223 · Compagnie Daher TB 30 EPSILON

10 Jun 2023 · Apache Junction, AZ, United States

Compagnie Daher TB 30 EPSILON · Accident: low altitude operation/event while maneuvering

From Falcon Field (FFZ) to Payson Airport (PAN)

Report a problem

Event

NTSB case
WPR23FA223
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Compagnie Daher TB 30 EPSILON

Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N759F
Operator
Unknown
Onboard fatalities
Unknown
Route
From Falcon Field (FFZ), Mesa, AZTo Payson Airport (PAN), Payson, AZ
Aircraft age
About 35 years (built 1988)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Maneuvering · low-altitude flying
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Low altitude operation/event
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The formation of three airplanes departed about 2 hrs and 20 minutes after sunrise to fly to an airport for lunch. The accident airplane was loaded with the pilot and a passenger, a full load of fuel, and an undetermined amount of baggage when they took off. The accident pilot, flying in the No. 2 position, intended to continue flying a solo cross-country after lunch. The flight planned to fly at low altitude around a local mountainous area en route to the lunch location. The No. 3 pilot reported that, during departure and before flying around the mountains, the accident airplane was having difficulty keeping up with the other two airplanes. Several witnesses observed the airplanes flying to the south along the west side of the mountains at a low altitude. They reported that the lead and No. 2 airplanes were close together, flying similar profiles, while the No. 3 airplane was further behind. Both pilots reported they struggled with depth perception when flying around the mountains. The No. 3 pilot reported that just before the accident, he observed the No. 2 airplane pass under his airplane from right to left toward the terrain. The nose of the airplane pitched up and down several times, but the trajectory of the airplane did not appear to change. He said the pilot of the No. 2 airplane did not make any radio calls or report any problems before the accident. A home security camera, facing east, captured the moment the No. 2 airplane impacted terrain. No airplanes were identifiable in the video. The video showed the west facing slopes of the mountains were shadowed and terrain features were not defined. It is possible the airplane was not performing as well as the other two airplanes due to its loading, but the evidence was insufficient to say whether that could have been a factor in the pilot’s ability to avoid the terrain. The evidence is consistent with the shadowing effects resulting from the positioning of the sun creating depth perception difficulties for the pilot. The pilot likely failed to recognize the significance of rising terrain in front of the airplane until there was insufficient time to avoid it, resulting in controlled flight into terrain. Contributing to the accident was the decision by all three pilots to fly at a low altitude around the mountainous terrain.

Probable cause

The pilot’s controlled flight into the mountainous terrain due to diminished depth perception as a result of the shadowing effect from the sun’s position. Contributing to the accident was the decision by all three pilots to fly low altitude around the mountainous terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR23FA223
Event ID
20230610192347
Case number
WPR23FA223
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 55d891048fb114fec3edbefee984fc3034296e64b34d899b8d6a41e3c3c011b4; retrieved 2026-09-15T08:01:08.272Z.