Sikorsky UH-60A N160AQ
23 November 2022 · San Diego, California, United States · No injuries
Summary
On 23 November 2022 at about 01:57 local time, a Sikorsky UH-60A registered N160AQ, operated by HeliStream Inc., was involved in an accident near San Diego, California, United States. 5 people were on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 01:57
- Classification
- Accident
- Location
- San Diego, California, United States
- Nearest airport
- Brown Field Municipal Airport (SDM)
- Coordinates
- 32.5727, -116.9803
- Aircraft
- Sikorsky UH-60A
- Registration
- N160AQ
- Category
- Helicopter
- Year built
- 1982
- Engines
- 2
- Operator
- HeliStream Inc.
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Instructional
- Phase of flight
- Not recorded
- Route
- El Cajon → Unknown
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Night
- NTSB number
- WPR23LA045
People
Nobody was injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 5 | 0 | 0 | 0 | 5 |
Probable cause
The failure of the crewmembers of the second helicopter to maintain visual separation with the first helicopter while complying with the LC controller’s instruction to go around. Contributing to the accident were the nighttime conditions and the lack of a safety alert from the controller to either helicopter.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
While conducting nighttime training at a tower-controlled airport, two helicopters were involved in a midair collision. A common practice at the airport was for the air traffic control tower (ATCT) local control controller (controller) to control helicopter operations on a non-movement portion of runway 26L called the underrun. The first helicopter to arrive was cleared for the option to land on the runway 26L underrun, at their own risk, but remained under control of the controller. The first helicopter flew one traffic pattern and then returned to the underrun and landed. The second helicopter arrived at the airport about 8 minutes later, and was cleared by the controller for the option to land on the runway 26L underrun. After the second helicopter crew reported that the first helicopter was in sight, the controller instructed them to “maintain visual separation” from the first helicopter, which the crew of the second helicopter acknowledged. While the first helicopter was on the underrun’s surface area preparing to take off, the second helicopter turned to the base leg of the traffic pattern. The controller believed that the second helicopter may have turned early and would possibly overfly the first helicopter, so he told the first helicopter that he needed him to take off; the pilot replied that they were taking off. The controller then made two radio calls to the second helicopter, one not received, and the other garbled. The controller then instructed the second helicopter to perform a go-around on the north side of runway 26L. While the pilot of the first helicopter was performing the takeoff, he saw the second helicopter overhead and attempted evasive action. While maneuvering, the main rotor blades of the first helicopter struck the second helicopter’s stabilator, which substantially damaged the main rotor blades of the first helicopter and the stabilator of the second helicopter. Both helicopters then landed on the airfield and shut down. The takeoff instructions for the first helicopter, followed by the go around instructions for the second helicopter, combined with the night conditions, likely created a scenario where the second helicopter crew lost visual contact with the first helicopter and overtook it from overhead. The controller was concerned that the second helicopter would overfly the first helicopter but did not issue a safety alert. The lack of a safety alert likely prevented the flight crews from understanding how close the helicopters were to each other, as well as their urgent need to take action to avoid a collision.
Quoted verbatim from the NTSB record.
Aircraft involved
| Aircraft | Registration | Operator | Damage |
|---|---|---|---|
| Sikorsky UH-60A | N160AQ | HeliStream Inc. | Substantial |
| Sikorsky MH-60R | 166583 | U.S. Navy | Substantial |
Other Sikorsky UH-60A accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 3 Dec 1994 | Sikorsky UH-60A | St. Petersburg, Florida, United States | U.s. Customs Service | No injuries | - |
| 14 Jul 1993 | Sikorsky UH-60A | Hortense, Georgia, United States | U.s. Customs Service | Fatal | 4 |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 2 Mar 2022 | Cessna 182D | Desert Camp, California, United States | Cloudstreet Flying Services | No injuries | - |
| 4 Sep 2022 | Bell 407 | Mount Baldy, California, United States | Air Methods Corp | Serious injuries | - |
| 16 Apr 2022 | Stoddard Hamilton GLASAIR SUPER II | Oxnard, California, United States | - | No injuries | - |
| 28 Dec 2022 | Embraer Executive EMB-505 | Hawthorne, California, United States | Solairus Aviation | No injuries | - |
| 10 Jun 2022 | Mooney M20K | Camarillo, California, United States | - | Fatal | 1 |
| 23 Jul 2022 | North American T-28B | Fallbrook, California, United States | Mach One Air Charters Inc | Fatal | 1 |