FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA22LA379 · Boeing A75N1

20 Aug 2022 · Bealeton, VA, United States

Boeing A75N1 and Boeing A75N1 · Accident: collision during takeoff/landing

Report a problem

Event

NTSB case
ERA22LA379
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
Event fatalities
Unknown
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

Aircraft 1 · Boeing A75N1

Aircraft type
Boeing A75
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
N55267
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 82 years (built 1940)
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
Landing · flare/touchdown
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
Collision during takeoff/landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Aircraft 2 · Boeing A75N1

Aircraft type
Boeing A75
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
N52652
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 80 years (built 1942)
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
Takeoff
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
Collision during takeoff/landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Organizational issues › Management
  • Personnel issues › Psychological

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

NTSB narrative

The vintage biplanes were operating at a private airport that provided airshows and airplane rides to the public. The pilot of the departing airplane taxied for takeoff and was number two behind another airplane that was taxiing ahead of him. At the same time, the pilot of the landing airplane was in the traffic pattern, preparing for landing. Local procedures required landing airplanes to make a low approach to signal airplanes taking off that a landing was imminent; the procedure was implemented because some airplanes at the airport were not equipped with radios. Landing aircraft had the right-of-way over aircraft taking off. The pilot of the landing airplane reported that he performed the required low approach, completed the traffic pattern, and proceeded onto final approach for landing. At the same time, the pilot of the departing airplane taxied onto the runway for takeoff and did not see the low approach by the landing airplane or his subsequent pattern. The pilot of the landing airplane did not see the departing airplane on the runway and landed on top of the departing airplane before the departing airplane became airborne. Both airplanes sustained substantial damage, the two pilots had minor injuries, and two passengers were not injured. Although both airplanes were equipped with radios, neither pilot was making radio calls; instead, they relied on the established visual traffic separation procedures only. A review of the airport’s standard operating procedures revealed that they did not address the use of radios or encourage pilots to use them if equipped. Following the accident, the airport made several modifications to their local procedures including recommending that all pilots of aircraft equipped with radios use them while in the traffic pattern; and moving the holding area short of the runway to another location that afforded better visibility of the traffic pattern.

Probable cause

The pilot of the departing airplane’s failure to see and avoid the landing airplane before takeoff, resulting in a collision with the landing airplane. Contributing was the airport’s failure to encourage pilots to use radios for traffic deconfliction when equipped.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA22LA379
Event ID
20220822105776
Case number
ERA22LA379
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: 7786d998d47ef8fc67ed43f16ba8926847aa4158dd9a446442657095892f38f0; retrieved 2026-09-13T18:38:41.341Z.