Student pilot reported an NMAC with a UAS while climbing with no time to react.

Date: 2025-02 · Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear · Phase: climb

Anomalies: airspace-violation-all-types|conflict-nmac|deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-unauthorized-flight-operations-uas|deviation-discrepancy-procedural-published-material-policy

Synopsis

Student pilot reported an NMAC with a UAS while climbing with no time to react.

Narrative

I had departed LGB 26L to ZZZ. GPS waypoints were LGB 26L - VPLQM - VPLHP - ZZZZZ - ZZZZZ1 - ZZZ XX. Climbing through 3500 feet about 7 NM south-southeast of LGB (between VPLQM and VPLHP; over the Long Beach practice area); I experienced a near-miss with a drone.I was climbing at 85-90 KIAS with a 10-knot tailwind. Looking outside to scan for traffic; I briefly observed a bright red; multi-rotor drone that flashed past me. It appeared to be about 50 feet off my left wing and 100 feet below my altitude. There was no warning. It appeared to be moving opposite direction; though given my airspeed; it could have been hovering. It took about 90 seconds for me to break in to the busy SoCal Departure frequency. Had the drone intersected my flight path; it could have caused a catastrophic midair collision; with probable impact to control surfaces; propeller; engine; fuel tank; or canopy. Had it impacted the canopy head-on; I would have been killed instantly.I suggest zero-tolerance enforcement against operators of drones that violate airspace restrictions throughout the NAS. There should be a mechanism for instantaneous reporting of drones so that operators can be apprehended immediately. Another effective countermeasure could be jamming of radio frequencies used to control drones. Thank you.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.