# Accident 20221122018182A: San Diego, CA, November 22, 2022

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 22, 2022, 17:50 local time
- Place: San Diego, CA
- Airport: Brown Field Municipal
- Damage: Minor damage
- Collision: Midair collision
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 32.5723° N, 116.9802° W: Placed by OpenAirDocs at BROWN FLD MUNI (SDM), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=32.5723&lon=-116.9802&mi=10
- Aircraft: NONE (not matched to a registry record)
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20221122018182A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

NAVY HELICOPTER CALL SIGN SEAHAWK 410 CONTACTED KSDM ATCT APPROXIMATELY FIVE MILES TO THE WEST OF THE AIRPORT.  SEAHAWK 410 WAS INSTRUCTED TO ENTER THE LEFT DOWNWIND FOR RUNWAY 26L AND ASKED, BY THE ATCT, IF THEY CAN ACCEPT THE UNDER-RUN OF 26L "AT THEIR OWN RISK". A FEW SECONDS AFTER THE SEAHAWK 410 ACCEPTED THE UNDER-RUN, ATCT CLEARED ^PRIVACY DATA OMITTED^ A UH-60A (C129) HELICOPTER FOR LANDING ON THE UNDER-RUN OF 26L. ATCT REQUESTED SEAHAWK 410 TO RECYCLE THEIR TRANSPONDER DUE TO THE CONTROLLER NOT RECEIVING THEIR MODE-C. ROUGHLY 5-10 SECONDS LATER SEAHAWK 410 RADIOED TO KSDM ATCT THAT THEY WERE "TROUBLE SHOOTING" THE TRANSPONDER. ATCT INSTRUCTED SEAHAWK 410 THAT THEY WERE NUMBER 2 BEHIND "THE HELICOPTER ON FINAL" FOR THE UNDER-RUN OF 26L (WHICH IS THE C129). SEAHAWK 410 INDICATED THAT C129 WAS INSIGHT AND WAS TOLD TO MAINTAIN VISUAL SEPARATION SEAHAWK 410 RESPONDED WITH "NAVY 410 COPIES ALL" KSDM ATCT INSTRUCTED C129 TO TAKE OFF BY SAYING "C129, I NEED YOU ON THE GO".  THE PILOTS OF C129 COMPLETED THE BEFORE TAKEOFF CHECKS AND INITIATED THE TAKEOFF.AS C129 WAS BEGINNING THE TAKEOFF, ACTC RADIOED TO SEAHAWK 410 THAT THE "COPTERCOPTER" ON THE GO IS FOR 26L" SEAHAWK 410 REQUESTED THE CONTROLLER SAY AGAIN. THE C129 CONTINUED ITS TAKEOFF AND WAS CLIMBING FROM THE UNDER-RUN AND WAS OVER RUNWAY 26L. ATC INSTRUCT SEAHAWK 410 TO GO AROUND ON THE NORTH SIDE OF 26L.  AS C129 CLIMBED THROUGH 200' AGL THE FLYING PILOT OBSERVED, THROUGH THE UPPER WINDOW, A HELICOPTER ABOVE HIM. THE PILOT LOWERED THE COLLECTIVE LEVER AND APPLIED RIGHT LATERAL CYCLIC TO AVOID A COLLISION. BOTH AIRCRAFT COLLIDED OVER RUNWAY 26L APPROXIMATELY 1/3 -1/2 WAY DOWN THE RUNWAY LENGTH.THE PILOTS OF C129 MADE ONE "MAYDAY" CALL, CONTINUED THEIR DESCENT AND LANDED BETWEEN RUNWAYS 26L&R. THE PILOTS CONDUCTED AN EMERGENCY SHUTDOWN OF THE ENGINES.SEAHAWK 410 LANDED AT THE FBO RAMP.

## Other aircraft in the event

- N160AQ, Sikorsky UH_60: no report for this aircraft; [N160AQ](https://openairdocs.org/aircraft/N160AQ) is registered now

## NTSB investigation

None matched to this report by aircraft and date. Search the NTSB's own records: https://data.ntsb.gov/carol-main-public/basic-search

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.