Plane crash map Locate crash sites, wreckage and more

N309CK accident description

California map... California list
Crash location Unknown
Nearest city Santa Ana, CA
33.745573°N, 117.867834°W
Tail number N309CK
Accident date 15 Dec 1993
Aircraft type Israel Aircraft Industries 1124A
Additional details: None

NTSB Factual Report

History of the Flight

On December 15, 1993, at 1733 hours Pacific standard time, an Israel Aircraft Industries 1124A, N309CK, experienced an in-flight loss of control and crashed about 3.5 nautical miles north of John Wayne Airport (SNA), Santa Ana, California. The airplane was on the final approach course for runway 19R. The pilot initially obtained an instrument flight rules (IFR) clearance, but was executing a visual approach at the time of the accident. The flight was an on-demand air taxi passenger operation under the provisions of Title 14 CFR Part 135 and was completing the final leg of a multileg passenger revenue operation.

The airplane, registered to Management Activities, Inc., Long Beach, California, and operated by Martin Aviation, Santa Ana, California, was destroyed by impact and the resulting postimpact fire. Both flight crewmembers and three passengers sustained fatal injuries; there were no ground injuries. Visual meteorological conditions prevailed. The Federal Aviation Administration's (FAA) various air traffic control tower records disclosed the airplane departed Long Beach Airport, Long Beach, California, on December 15, 1993, at 0700 hours to begin the multileg operation. The last flight leg departed Brackett Airport, La Verne, California, at 1713 hours.

National Transportation Safety Board investigators reviewed the recorded radio communications between N309CK, Coast terminal radar approach control (TRACON), and the John Wayne Airport air traffic control tower (ATCT). The review revealed that before departing Brackett Airport the flightcrew requested and received a local tower en route IFR clearance to John Wayne Airport.

After departing Brackett Airport, the flight contacted the FAA, Ontario [California] TRACON and received radar vectors toward John Wayne Airport. At 1728 hours, the Ontario TRACON sector controller instructed the flight to contact Coast TRACON.

According to the cockpit voice recorder (CVR), at 1727:41 hours, the first officer received the automated terminal information service (ATIS) "zulu." [The times noted for the CVR information differ from the FAA ATC communications transcripts; the CVR information was adjusted in this report to match the ATC transcripts.] At 1728:34 hours, the flight contacted the Coast TRACON Tustin Radar sector controller and reported "...climbing to four thousand..." [feet - all altitudes in this report are mean sea level altitudes]. The sector controller instructed the flight to reduce its speed to 170 knots; the flight's first officer acknowledged the clearance. The cockpit voice recorder established that the first officer made all the transmissions to the sector controller.

The sector controller had previously instructed a preceding airplane, also landing at John Wayne Airport, to reduce its speed to 170 knots. This aircraft was United Airlines flight 103 (UAL 103), a Boeing 757-200. The Tustin Radar computer data readout (CDR) showed that N309CK was at 3,700 feet.

At 1729:09 hours, the first officer contacted Martin Aviation and informed the dispatcher that the flight would be landing within ten minutes and would need fuel. At 1730:05 hours, the sector controller instructed the flight to turn to a 100-degree heading (all headings/bearings in this report are oriented toward magnetic north). He then stated, "westwind nine charlie kilo [is] following a united boeing jet on base [leg at] two o'clock four miles southeast bound [at] four thousand [feet] descending." The first officer responded, "in sight charlie kilo."

At 1730:12 hours, the sector controller instructed N309CK to "...follow that traffic cleared visual approach runway one niner right reduce speed to follow he's [UAL 103] slowing through a hundred and seventy [knots]." The first officer acknowledged the clearance and the traffic [UAL 103]. The sector controller then instructed UAL 103, "...cleared visual approach runway one niner right reduce speed to one five zero and contact the tower...." UAL 103 responded that the flight was below 150 knots. The CDR showed that N309CK was at 3,900 feet, and about 3.8 nautical miles to the left (north) of UAL 103 which was at 3,800 feet.

At 1730:26 hours, the first officer then told the captain "...eh he's pretty close...." The captain responded, "...okay I'm ah lets go flaps twelve." The CDR showed that at this time N309CK was at 3,900 feet and about 3.3 nautical miles to the left (north) of UAL 103 which was now about 3,700 feet.

The first officer then pointed out UAL 103 to the captain. The captain responded, "...I got him - okay we can do it...no problem." At 1730:42 hours, the sector controller advised N309CK that "...traffic you're following is at a hundred and fifty knots you can s-turn as necessary to follow that traffic contact john wayne tower...." At 1730:49 hours, the first officer responded, "ok we'll slow it up and do what we have to...."

Meanwhile, at 1730:47 hours, UAL 103 contacted the John Wayne ATCT local controller and reported "...turning final abeam lemon." At 1731:01 hours, N309CK contacted the local controller and reported, "...on a visual behind the ah i believe it's united ...." The CVR indicated a sound similar to the landing gear being lowered. The local controller responded, "westwind three zero nine charlie kilo john wayne tower number three behind the united he's indicating thirty knots slower." The first officer responded, "ok we're slowing ah three zero nine charlie kilo." The CDR now indicated that N309CK was at 3,700 feet and about 2.2 miles behind or north of UAL 103 which was about 3,100 feet.

There were no further communications between N309CK and the FAA air traffic control facility. The CVR showed that the flightcrew proceeded to complete the prelanding checklist and that the landing gear was fully extended. At 1731:43 hours, the captain told the first officer that he was going to slow the airplane to Vref (123 knots) and that he was going to descend the airplane at that speed.

The first officer then told the captain that UAL 103 was "...a little too high on the ah...." The captain responded, "...yeah we'll just sit here and slow down...." He also said, "...I'll slightly "s" [turn] back and forth...", and later said, "...we'll run this a dot high [fly the glide slope one dot above the three degree glide slope]...." The first officer responded, "...yeah we might still get a little wake turbulence there...." At 1732:31 hours, the first officer remarked, "I don't know looks kinda close." The captain responded, "yeah it's close but I think we'll be okay."

At this time, the CVR indicated that both pilots saw UAL 103, and the captain asked the first officer, "what are the surface winds." The first officer responded, "two hundred degrees at ah six knots."

At 1733:02 hours, the captain queried the first officer, "...and we got gear and full flaps...." The first officer responded, "yup yaw damper will complete it...."

At 1733:10 hours, the CVR indicated that the captain took a deep breath, which was followed by the first officer saying, "keep it goin' around keep it goin' around...." The CVR recording ended at 1733:15 hours.

The last CDR radar target on N309CK was at 1733:07 hours. At this time, N309CK was at 1,100 feet, 2.1 nautical miles behind UAL 103.

Safety Board investigators interviewed several ground witnesses. The consensus of the witnesses was that while on final approach the airplane suddenly pitched downward, rolled 360 degrees about its longitudinal axis, and crashed. Two witnesses, both commercial pilots, reported seeing sparks/flames emanating from the airplane during the accident sequence. Other witnesses reported a strange whining sound emanating from the airplane.

Crew Information

Captain:

The captain was an employee of Management Activities, Inc., and was trained under the provisions of the operator's Title 14 Part 135 Air Taxi Certificate. According to the operator, the pilot always flew the airplane as the captain when the accident airplane was used in connection with the operator's air taxi operations. The operator would provide the second-in-command (SIC) during these operations.

The captain held an airline transport pilot certificate with airplane multiengine land, CE-500, HS-125, CL-600, and IA-Jet type ratings. The certificate was endorsed for commercial privileges with an airplane, single-engine land rating. He also held a first-class medical certificate dated December 3, 1993; the certificate contained a "must have corrective lenses" limitation endorsement.

Safety Board investigators did not obtain the captain's personal flight hours logbook. The flight hours reflected in this report were provided by the operator. According to the operator, the pilot accrued 8,227.5 total flight hours. The captain accrued 756 hours in the accident airplane make and model of which 700 hours were logged as pilot-in-command.

According to the captain's training records provided by the operator, the pilot satisfactorily completed a 6-month recurrent training flight on July 8, 1993, conducted by SimuFlite, Dallas-Fort Worth Airport, Texas, in a Westwind II simulator. On August 27, 1993, the pilot satisfactorily completed an annual recurrent training flight conducted by the operator in a Beech F-90, a turbopropeller driven airplane.

First Officer (F/O):

The F/O was an employee of the operator. The operator conducted all of his required training and recurrency flight tests. The training and flight tests were accomplished under the supervision of the FAA, Long Beach Flight Standards District Office.

The F/O held an airline transport pilot certificate with airplane multiengine land, CE-650, LR-Jet, and IA-Jet type ratings. The certificate was endorsed for commercial privileges with an airplane, single-engine land rating. He also held an unrestricted first-class medical certificate which was issued on September 3, 1993.

Safety Board investigators did not obtain the F/O's personal flight hours logbook. The flight hours reflected in this report were provided by the operator. According to the operator, the pilot accrued 5,447 total flight hours. The F/O accrued 136 hours in the accident airplane make and model of which 70 hours were logged as pilot-in-command.

According to the operator, the F/O was qualified as pilot-in-command in a Lear 35, Beech F-90, and the accident airplane make and model. A review of the F/O's flight training records revealed that the F/O received his last flight and ground recurrency training in a Lear 35A on August 15 and August 23, 1993, respectively. The F/O received his last transition/recurrent ground and flight training in the accident airplane on December 22, 1992.

Martin Aviation's Director of Operations told Safety Board investigators that the company's training syllabus does not include wake turbulence avoidance. The training syllabus does address windshear avoidance and other meteorological phenomenon. SimuFlite, Dallas-Fort Worth Airport, Texas, provided the Safety Board with the captain's flight training records. A review of the records revealed the captain's simulator and ground school training complied with the required training syllabus. Wake turbulence avoidance was not included; nor was it required.

Aircraft Information

The registered owner, Management Activities, Inc., maintained the airplane and provided the Safety Board with the airplane's maintenance records. Company maintenance personnel maintained the airplane in accordance with the manufacturer's inspection program as approved by the FAA, Long Beach Flight Standards District Office.

The maintenance personnel performed the last 150-hour inspection on June 10, 1993. At the time of the accident, the airplane accrued 3,027 hours (including the flights made on the day of the accident), which was 95 hours since the last inspection.

Communications

There were no reported communications difficulties between N309CK and any FAA air traffic control facility.

The Safety Board investigators from the Office of Research Engineering found the cockpit voice recorder (CVR) recording medium undamaged. The recording started at 1702:29 hours and continued uninterrupted until 1733:15 hours (as adjusted). A review of the recorded ground operations at Brackett Airport were reviewed and found to be routine and were not transcribed. Safety Board investigators made a transcript of the crew receiving their IFR clearance and their departure from Brackett Airport. The transcript continued from the flight's departure until the crash.

Radar Data

Radar data from various radar facilities were obtained and plotted. The flight profile radar track shows that at a point 7 nautical miles from the airport, N309CK's flight path was consistently below UAL 103. When N309CK was about 3.5 nautical miles from the airport, its flight path was about 400 feet below UAL 103's flight path and was about 2.1 miles in-trail. The glide path for N309CK and UAL 103 was 3 degrees and 5.6 degrees, respectively.

Wreckage and Impact Information

The airplane crashed in a vacant lot next to multiple surrounding buildings and was about 100 feet to the right of the John Wayne Airport runway 19R extended centerline. Ground scars and the wreckage examination showed that the airplane struck the ground in about a 45-degree nose-down, wings level attitude, with the nose of the airplane facing about 165 degrees. The airplane's flight path was about 80 degrees downward. Debris from the airplane's wreckage was found scattered from the main impact crater outward to about 100 feet in a 30-degree arc tangential to the centerline of the airplane.

All of the airplane's major components and flight control surfaces were found at the main impact area. The cabin area was incinerated by the postimpact fire/explosion. A 6-foot section of the upper cabin area was found about 30 feet south of the main wreckage area.

Both wings separated from their respective wing-to-fuselage attach fittings and remained next to the fuselage.

Continuity of the flight control surfaces could not be determined due to impact and postimpact fire damage. The flight controls, however, remained connected at their respective attach points.

The empennage was found about 2 feet forward of the main wreckage. The horizontal/vertical stabilizer connecting rod bolt was missing, but the inner section of the eyebolts displayed gouging signatures. The stabilizer trim actuator was found extended 10.45 inches from the actuator body. According to the manufacturer, this extension corresponds to a minus 4.2-degree horizontal stabilizer trim setting or full nose-up.

Both flaps were damaged, but remained partially connected at their wing flap track assemblies. The flap motor actuators on the left and right wing were found extended 6.875 and 7 inches, respectively. According to the manufacturer, these measurements correspond to a 40-degree flap extension or flaps fully extended.

Both main landing gear actuators were found fully extended which corresponds to a landing gear-down position. The nose landing gear actuator was not found.

Both fuel tanks interconnect valves were found and examined. One valve was open and the other was closed. The closed valve is designed so that it could be manually closed; the other valve is electrically controlled and cannot be manually closed.

Both engines' shutoff valves were found in the open position. The upper fuselage auxiliary tank valve is the same type of valve as the engine fuel shutoff valves and was found in the closed position.

Fire

The Santa Ana Fire Department arrived at the accident site at 1743 hours. The battalion chief reported that fire personnel did not encounter any difficulties in extinguishing the fire. The fire was suppressed at 1758 hours.

Medical and Pathological Information

The Orange County Medical Examiner/Coroner's Office performed postmortem examinations on both pilots. The pathologist reported that neither pilot had any condition or disease which would have affected his capability to perform his duties.

The FAA, Civil Aeromedical Institute (CAMI), Oklahoma City, Oklahoma, conducted toxicolog

NTSB Probable Cause

THE PILOT-IN-COMMAND'S FAILURE TO MAINTAIN ADEQUATE SEPARATION BEHIND THE BOEING 757 AND/OR REMAIN ABOVE ITS FLIGHT PATH DURING THE APPROACH, WHICH RESULTED IN AN ENCOUNTER WITH WAKE VORTICES FROM THE 757. FACTORS RELATED TO THE ACCIDENT WERE: AN INADEQUACY IN THE ATC PROCEDURE RELATED TO VISUAL APPROACHES AND VFR OPERATIONS BEHIND HEAVIER AIRPLANES, AND THE RESULTANT LACK OF INFORMATION TO THE WESTWIND PILOTS FOR THEM TO DETERMINE THE RELATIVE FLIGHT PATH OF THEIR AIRPLANE WITH RESPECT TO THE BOEING 757'S FLIGHT PATH.

© 2009-2020 Lee C. Baker / Crosswind Software, LLC. For informational purposes only.