20171226023799A

Accident · Substantial damage

FAA accident report · Cessna 182S · Santa Ana, CA · December 26, 2017

Date
December 26, 2017 · 13:40 local
Place
Santa Ana, CA
Phase of flight
Taxi
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N698MC
NTSB investigation
NTSBWPR18CA059
Reported as
Cessna 182S
Reported engine
Lycoming I0360 SER A&C
People aboard
1
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Private pilot
Pilot’s flight hours
640 total25 in this make and model25 in the last 90 days

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.

On 12/26/17 this office was notified of the accident. Inspector privacy data omitted with lgb FSDO traveled to the scene of the accident and met the pilot, privacy data omitted. privacy data omitted Was provided with and explained the pilots bill of rights.

According to privacy data omitted he departed Oklahoma on December 25, 2017 for sna. On the day of the incident he flew from tus to sna. According to privacy data omitted he was a "bit intimidated" by the complexity of the airspace around ksna. privacy data omitted Stated that as he approached ksna, ATC asked him if he had the airport in sight, he reported he did. He was advised of a jet traffic on the right runway (20R) and was cleared to land on runway 20L. According to privacy data omitted he was concerned about the wake generated by the jet traffic and he maintained higher than normal approach path. privacy data omitted Stated that he was high and fast on the approach. privacy data omitted Further stated that he thought that he can get the aircraft on speed and on the approach path using flaps, but was unable to do so. The aircraft touched down on runway 20L between taxiway juliet and taxiway hotel, and rolled through the departure end into the runway overrun area. privacy data omitted Stated that he was pretty shook up after the landing. He further stated that after the landing he was instructed to taxi on taxiway hotel and taxiway alpha towards atlantic aviation. privacy data omitted Also stated that after turning right on taxiway hotel he mistakenly turned left on taxiway alpha and at that time ATC instructed him to perform a 180° turn on taxiway alpha. According to privacy data omitted when he made the 180° turn on taxiway alpha he saw jet traffic taxing towards him. While maneuvering on taxiway alpha to avoid jet traffic his left wing inadvertently struck an unoccupied guard shack in the non-movement area.

As the FAA filed it

ON 12/26/17 THIS OFFICE WAS NOTIFIED OF THE ACCIDENT. INSPECTOR ^PRIVACY DATA OMITTED^ WITH LGB FSDO TRAVELED TO THE SCENE OF THE ACCIDENT AND MET THE PILOT, ^PRIVACY DATA OMITTED^. ^PRIVACY DATA OMITTED^ WAS PROVIDED WITH AND EXPLAINED THE PILOTS BILL OF RIGHTS.

ACCORDING TO ^PRIVACY DATA OMITTED^ HE DEPARTED OKLAHOMA ON DECEMBER 25, 2017 FOR SNA. ON THE DAY OF THE INCIDENT HE FLEW FROM TUS TO SNA. ACCORDING TO ^PRIVACY DATA OMITTED^ HE WAS A "BIT INTIMIDATED" BY THE COMPLEXITY OF THE AIRSPACE AROUND KSNA. ^PRIVACY DATA OMITTED^ STATED THAT AS HE APPROACHED KSNA, ATC ASKED HIM IF HE HAD THE AIRPORT IN SIGHT, HE REPORTED HE DID. HE WAS ADVISED OF A JET TRAFFIC ON THE RIGHT RUNWAY (20R) AND WAS CLEARED TO LAND ON RUNWAY 20L. ACCORDING TO ^PRIVACY DATA OMITTED^ HE WAS CONCERNED ABOUT THE WAKE GENERATED BY THE JET TRAFFIC AND HE MAINTAINED HIGHER THAN NORMAL APPROACH PATH. ^PRIVACY DATA OMITTED^ STATED THAT HE WAS HIGH AND FAST ON THE APPROACH. ^PRIVACY DATA OMITTED^ FURTHER STATED THAT HE THOUGHT THAT HE CAN GET THE AIRCRAFT ON SPEED AND ON THE APPROACH PATH USING FLAPS, BUT WAS UNABLE TO DO SO. THE AIRCRAFT TOUCHED DOWN ON RUNWAY 20L BETWEEN TAXIWAY JULIET AND TAXIWAY HOTEL, AND ROLLED THROUGH THE DEPARTURE END INTO THE RUNWAY OVERRUN AREA. ^PRIVACY DATA OMITTED^ STATED THAT HE WAS PRETTY SHOOK UP AFTER THE LANDING. HE FURTHER STATED THAT AFTER THE LANDING HE WAS INSTRUCTED TO TAXI ON TAXIWAY HOTEL AND TAXIWAY ALPHA TOWARDS ATLANTIC AVIATION. ^PRIVACY DATA OMITTED^ ALSO STATED THAT AFTER TURNING RIGHT ON TAXIWAY HOTEL HE MISTAKENLY TURNED LEFT ON TAXIWAY ALPHA AND AT THAT TIME ATC INSTRUCTED HIM TO PERFORM A 180° TURN ON TAXIWAY ALPHA. ACCORDING TO ^PRIVACY DATA OMITTED^ WHEN HE MADE THE 180° TURN ON TAXIWAY ALPHA HE SAW JET TRAFFIC TAXING TOWARDS HIM. WHILE MANEUVERING ON TAXIWAY ALPHA TO AVOID JET TRAFFIC HIS LEFT WING INADVERTENTLY STRUCK AN UNOCCUPIED GUARD SHACK IN THE NON-MOVEMENT AREA.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.