20221120021139I

Incident · Minor damage

FAA incident report · David Weinberg SONEX B · Oakland, CA · November 20, 2022

Date
November 20, 2022 · 15:12 local
Place
Oakland, CA
Airport
Oakland Airport
Phase of flight
Descent
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N5784N
Reported as
David Weinberg Sonex B
Reported engine
Ulpower 350I
People aboard
1
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Private pilot
Pilot’s flight hours
460 total

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

At 2312 zulu time, privacy data omitted was in the air for approximately 45 minutes while performing an engine break in. It was flying right rectangular patterns at 1500 feet MSL. An aircraft was on final for runway 28R at roughly 2312 zulu. privacy data omitted Requested 1000 feet. ATC asked if he wanted to come inbound to land, or if he wanted to continue his pattern at 1000 feet. privacy data omitted Stated he wanted to come inbound to land. ATC instructed privacy data omitted to remain at 1500 feet for the inbound aircraft. When privacy data omitted was over the 28R numbers, ATC instructed him to descend to 1000 feet and avoid traffic for 28R. privacy data omitted Did not reply. ATC repeated this transmission with no reply. ATC noticed on radar that his target had 000 as his altitude, and then noticed privacy data omitted was in a right tun, roughly mid-field and low. ATC instructed privacy data omitted to climb, but again received no response. The inbound aircraft was on a very short final, just over the numbers of 28R, when I realized privacy data omitted was an emergency. ATC noticed it was apparent that privacy data omitted was turning towards runway 28R. ATC cleared privacy data omitted to land on 28L to keep runway separation with the inbound aircraft. When it was apparent that privacy data omitted was attempting to set it down on 28R. privacy data omitted Landed left of 28R. Emergency vehicles were called to 28R and the runway was closed.

As of now I consider this incident closed. If more informaiton is presented, the report will be amended.

As the FAA filed it

AT 2312 ZULU TIME, ^PRIVACY DATA OMITTED^ WAS IN THE AIR FOR APPROXIMATELY 45 MINUTES WHILE PERFORMING AN ENGINE BREAK IN. IT WAS FLYING RIGHT RECTANGULAR PATTERNS AT 1500 FEET MSL. AN AIRCRAFT WAS ON FINAL FOR RUNWAY 28R AT ROUGHLY 2312 ZULU. ^PRIVACY DATA OMITTED^ REQUESTED 1000 FEET. ATC ASKED IF HE WANTED TO COME INBOUND TO LAND, OR IF HE WANTED TO CONTINUE HIS PATTERN AT 1000 FEET. ^PRIVACY DATA OMITTED^ STATED HE WANTED TO COME INBOUND TO LAND. ATC INSTRUCTED ^PRIVACY DATA OMITTED^ TO REMAIN AT 1500 FEET FOR THE INBOUND AIRCRAFT. WHEN ^PRIVACY DATA OMITTED^ WAS OVER THE 28R NUMBERS, ATC INSTRUCTED HIM TO DESCEND TO 1000 FEET AND AVOID TRAFFIC FOR 28R. ^PRIVACY DATA OMITTED^ DID NOT REPLY. ATC REPEATED THIS TRANSMISSION WITH NO REPLY. ATC NOTICED ON RADAR THAT HIS TARGET HAD 000 AS HIS ALTITUDE, AND THEN NOTICED ^PRIVACY DATA OMITTED^ WAS IN A RIGHT TUN, ROUGHLY MID-FIELD AND LOW. ATC INSTRUCTED ^PRIVACY DATA OMITTED^ TO CLIMB, BUT AGAIN RECEIVED NO RESPONSE. THE INBOUND AIRCRAFT WAS ON A VERY SHORT FINAL, JUST OVER THE NUMBERS OF 28R, WHEN I REALIZED ^PRIVACY DATA OMITTED^ WAS AN EMERGENCY. ATC NOTICED IT WAS APPARENT THAT ^PRIVACY DATA OMITTED^ WAS TURNING TOWARDS RUNWAY 28R. ATC CLEARED ^PRIVACY DATA OMITTED^ TO LAND ON 28L TO KEEP RUNWAY SEPARATION WITH THE INBOUND AIRCRAFT. WHEN IT WAS APPARENT THAT ^PRIVACY DATA OMITTED^ WAS ATTEMPTING TO SET IT DOWN ON 28R. ^PRIVACY DATA OMITTED^ LANDED LEFT OF 28R. EMERGENCY VEHICLES WERE CALLED TO 28R AND THE RUNWAY WAS CLOSED.

AS OF NOW I CONSIDER THIS INCIDENT CLOSED. IF MORE INFORMAITON IS PRESENTED, THE REPORT WILL BE AMENDED.