# Accident 20220820020112A: Boeing A75N1(PT17), Bealton, VA, August 20, 2022 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: August 20, 2022, 09:07 local time - Place: Bealton, VA - Airport: Flying Circus Aerodrome - Damage: Substantial damage - Collision: Collision on the ground - Phase of flight: Landing: Touchdown - Operating rules: General operating rules (Part 91) - Location: 38.5522° N, 77.7153° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=38.5522&lon=-77.7153&mi=10 - Aircraft: N55267, a cancelled registration (https://openairdocs.org/deregistered/N55267-2024-08-24) (OpenAirDocs) - Registry model: Boeing A75N1(PT17) (registry code 1380134, https://openairdocs.org/model/boeing-a75n1-pt17) (OpenAirDocs) - Registry engine: Continental W670 series (registry code 17018, https://openairdocs.org/engine/continental-w670-series) (OpenAirDocs) - Reported make and model: BOEING A75N1(PT17) - Reported engine: CONT MOTOR W670 SERIES - People aboard: 2 - Fatal injuries: 0 - Other injuries: 1 - Pilot certificates: Commercial pilot, flight instructor - Pilot flight hours: 5,920 total - NTSB investigation: [NTSB ERA22LA379](https://openairdocs.org/ntsb/ERA22LA379) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20220820020112A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. INVESTIGATION. LANDING AIRPLANE COMPLETED A PASSENGER RIDE, FINISHING UP AT AROUND 1,500 FT AGL NEAR THE AIRPORT. HE CHECKED THE PATTERN FOR OTHER AIRCRAFT WHILE MAKING A FEW STEEP TURNS. SEEING THAT THE PATTERN WAS CLEAR, HE APPROACHED THE NORTHERN END OF THE RUNWAY IN A SHALLOW DIVE AND MADE A LOW PASS AT APPROXIMATELY 100 TO 200 FEET AGL OVER THE RIGHT SIDE OF THE RUNWAY, HEADING TO THE SOUTH. HE THEN STARTED A CLIMB PRIOR TO THE END OF THE RUNWAY AND TURNED TO THE RIGHT MAKING A 180-DEGREE CLIMBING COURSE CHANGE INTO THE RIGHT DOWNWIND PER NORMAL OPERATIONS AT THE FLYING CIRCUS AERODROME DURING RIDE OPERATIONS. THE PROCEDURE FOR PATTERN OPERATIONS AT THE TIME OF THE INCIDENT WAS TO MAKE A LOW PASS BEFORE LANDING TO SIGNAL TO DEPARTING AIRCRAFT THAT THE PILOT INTENDED TO LAND. WHEN AN AIRPLANE ON THE GROUND OBSERVES THE LOW PASS BY THE AIRPLANE INTENDING TO LAND, THEY ARE REQUIRED TO HOLD SHORT OF THE END OF THE RUNWAY UNTIL THE LANDING AIRPLANE HAS LANDED AND CLEARED THE RUNWAY, THEN THEY ARE ALLOW TO DEPART. THIS PROCEDURE HAS BEEN A LONG-STANDING PROCEDURE IN EFFECT AT THE AIRPORT DUE TO THE FACT THAT THERE IS A MIX OF AIRPLANES THAT OPERATE THERE THAT ARE NOT RADIO EQUIPPED. AT THE TIME OF THE INCIDENT, THE PILOT INTENDING TO LAND OBSERVED AN AIRPLANE DEPARTING FROM THE RUNWAY TOWARDS THE SOUTH AND A SECOND AIRPLANE SITTING AT THE END OF THE RUNWAY WAITING FOR TAKEOFF. LANDING AIRPLANE CONTINUED TO FLY THE DOWNWIND FOR THE APPROACH AND TURNED RIGHT BASE. HE REMAINED CLOSE TO THE RUNWAY WITH HIS PATTERN AS REQUIRED, SO THAT HE COULD BE OBSERVED BY OTHER PLANES ON THE GROUND. HE AGAIN CHECKED THE RUNWAY FROM THE BASE LEG, NOTED IT WAS CLEAR, AND TURNED FINAL, APPROACHING THE TREES AT THE APPROACH END OF THE RUNWAY. HE AGAIN OBSERVED THAT THE RUNWAY AHEAD OF HIM WAS CLEAR AND INITIATED HIS FINAL DESCENT FOR LANDING AFTER PASSING OVER THE TREES ON THE APPROACH END OF THE RUNWAY. LANDING AIRPLANE MAINTAINED A SPEED OF APPROXIMATELY 65 TO 70 MPH WITH HIS ENGINE AT IDLE BY THIS TIME. SUDDENLY HE OBSERVED DEPARTING AIRPLANE UNDER THE RIGHT SIDE OF THE AIRPLANE JUST AS THEY COLLIDED. DEPARTING AIRPLANE WAS SLIGHTLY TO HIS RIGHT, CAUSING HIM TO DESCEND ONTO ITS TOP LEFT WING. HIS AIRPLANE DECELERATED RAPIDLY, THERE WAS NOISE OF THE COLLISION, AND HIS PLANE TURNED ABOUT 90 DEGREES TO THE RIGHT AND STOPPED. DEPARTING AIRPLANE AT THAT TIME HAD COME TO REST UPSIDE DOWN NEARLY RIGHT IN FRONT OF THE NOSE OF HIS AIRPLANE. ONCE ALL MOTION HAD CEASED, THE PILOT CHECKED HIS PASSENGER, WHO HAD MINOR OR NO INJURIES, AND MOVED TO A SAFE LOCATION. HE ALSO CHECKED THE PILOT AND PASSENGER OF THE OTHER AIRPLANE WHO WERE OK WITH APPARENT MINOR INJURIES. THE PILOT SECURED THE ACCIDENT PLANE BY SHUTTING OFF ALL ELECTRICAL SWITCHES, THE MAG SWITCH AND FUEL SHUTOFF. THERE WAS NO FUEL LEAKING FROM EITHER AIRPLANE, AND THERE WAS NO FIRE OR SMOKE. THE FLYING CIRCUS GROUND CREW AND OTHER FIRST RESPONDER PERSONNEL RESPONDED WITHOUT DELAY. ## Other aircraft in the event - N52652, Boeing A75N1(PT17): [Accident 20220820020162A](https://openairdocs.org/incident/20220820020162A) ## The NTSB's investigation of this event (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB ERA22LA379](https://openairdocs.org/ntsb/ERA22LA379), Aug 20, 2022: Boeing A75N1 (N55267), Bealeton, VA, substantial damage. 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… ## Other reports on N55267 (1) Matched to the same aircraft by N-number and date. - [Accident 20060529010879A](https://openairdocs.org/incident/20060529010879A), May 29, 2006: Boeing A75N1 (N55267), South Hill, VA, Minor damage. (-23) Pilot reported, as he entered the rollout phase of landing, in which all three landing gear were on the ground, he lost directional control of the… From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.