LAX04FA205

NTSB accident investigation · Piper PA-44-180 · Julian, CA · May 11, 2004

Accident · FatalField investigationFinal report
Date
May 10, 2004, 21:00 local (May 11, 2004, 04:00 UTC)
Place
Julian, CA
Injuries
2 fatal
Damage
Destroyed
Phase of flight
Enroute
Aircraft
N304PAPiper PA-44-180
Weather
Visual (VMC) · Night/dark
Status
Completed · report December 28, 2004
Report
Approved by Office Director
Parties
Textron-Lycoming, Federal Aviation Administration, The New Piper Aircraft Company
FAA report
20040510009799A
Case key
59196

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The incorrect use of an abbreviated callsign by the TRACON sector radar controller to issue a descent clearance to N434PA and the sector controllers failure to detect that the clearance had been read back with the full callsign by the pilot of N304PA. Also causal was the pilots failure to question a clearance that descended them below the published Minimum En route Altitude (MEA). Contributing to the accident was the failure of both the Center and TRACON controllers to properly respond to the aural and visual Minimum Safe Altitude Warning System (MSAW) alert.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

In flight collision with terrain/waterCruise
Light condition - dark nightFactor
Terrain condition - mountainous/hilly
Atc clearance - improperAtc personnel(dep/apch)Cause
Atc clearance - not verifiedFlightcrewCause
Unsafe/hazardous condition warning - not coordinated/diseminatedAtc personnel(dep/apch)Factor

Analysis

The twin engine airplane collided with rising mountainous terrain while in cruise flight on an IFR clearance. The airplane, N304PA, was on a night IFR flight and was number four in a trail of five company airplanes flying the same route. The time separation between each airplane was about 5 to 10 minutes. The airplane directly ahead of N304PA was N434PA. After being handed off from Los Angeles Center, the flight crew of N304PA contacted the TRACON sector controller at 2043:48 PDT, reporting level at 8,000. The TRACON sector controller instructed the pilot to fly heading 260 after the Julian VOR and intercept the localizer. At 2045:47, the TRACON sector controller told the pilot of N434PA to descend to 6,000 feet. The pilot of N434PA acknowledged the clearance. At 2047:55, the sector controller transmitted, "Seminole four papa alpha descend and maintain five thousand two hundred." The pilot of N304PA responded, "Down to five thousand two hundred for three zero four papa alpha." According to information provided by the TRACON sector controller, this clearance was intended for N434PA. The controller did not recognize that the clearance had been acknowledged by N304PA rather than N434PA. At 2049:55, the pilot of N304PA reported that he had ATIS information Zulu and the sector controller responded, "Seminole three zero four papa alpha thank you very much." At that time the data block on the TRACON controller's display was showing N304PA descending through about 6,600 feet. The Minimum Enroute Altitude for the airway segment being flown was 7,700 feet. At 2050:27, the sector controller again cleared N434PA to descend and maintain 5,200 feet. A Minimum Safe Altitude Warning (MSAW) alert on N304PA was presented to the Center controller at 2049:03. The aircraft's data block remained on the Center controllers display until the radar controller forced it off at 2050:07. The Center controller did not notify the TRACON sector controller that he was receiving a MSAW alert as required by FAA directives. The TRACON's MSAW system generated two predicted altitude alerts on the accident airplane at 2050:46 and 2050:51. According to FAA MSAW documentation, two consecutive predicted alerts will initiate an MSAW warning to the controller working the affected aircraft. Collectively, these alerts would have caused a 5 second aural alert to the sector controller beginning at 2050:51, along with a flashing red "LA" in N304PA's data block from 2050:51 until about 2051:06. The aircraft then descended below radar coverage, the track went into coast status, and the alert terminated. The wreckage of N304PA was located on a ridgeline 200 yards south of the Julian VOR at 5,537 feet msl. No preimpact airplane mechanical anomalies were identified.

Factual narrative

1.1 History of flight

On May 10, 2004, about 2051, Pacific daylight time, a Piper PA-44-180, N304PA, collided with mountainous terrain at Julian, California. The airplane was operated by Pan Am International Flight Academy under the provisions of 14 CFR Part 91. Both private pilots were fatally injured and the airplane was destroyed. Visual meteorological conditions prevailed and an instrument flight plan had been filed. The flight originated at Deer Valley, Arizona.

The airplane was on an IFR flight from Phoenix Deer Valley Airport, Phoenix, Arizona, to McClellan-Palomar Airport, Carlsbad, California. The airplane took off from Deer Valley at 1932 Pdt and the cleared route of flight was; Gila Bend, V66, Imperial, V458, Julian, then direct to Palomar. N304PA was number four in a train of five company airplanes flying the same route. The time separation between each airplane was about 5 to 10 minutes. The airplane directly ahead of N304PA was N434PA.

Review of Air Traffic Control communications and radar data shows that the flight crew of N304PA contacted the San Diego North Radar (SDNR) controller at 2043:48 Pdt, reporting level at 8,000. The SDNR controller instructed the pilot to fly heading 260 after Julian and intercept the (Palomar) localizer. The pilot read back the clearance. At 2045:47, the SDNR controller told the pilot of N434PA, another Piper Seminole ahead of N304PA and flying the same route, to descend to 6,000 feet. The pilot of N434PA acknowledged the clearance. At 2047:55, the SDNR controller transmitted, "Seminole four papa alpha descend and maintain five thousand two hundred." The pilot of N304PA responded, "Down to five thousand two hundred for three zero four papa alpha." According to information provided by the approach controller, this clearance was intended for N434PA. The controller did not recognize that the clearance had been acknowledged by N304PA rather than N434PA. At 2048:19, the pilot of N434PA transmitted, "…for four three four papa alpha?" (The beginning of the transmission was blocked by another transmission from the SDNR controller to an uninvolved aircraft.) The SDNR controller replied, "No. Duke six romeo tango heading one nine zero maintain eight thousand."

At 2049:55, the pilot of N304PA reported that he had ATIS information Zulu at Palomar, and the SDNR controller responded, "Seminole three zero four papa alpha thank you very much." According to radar data, at that time N304PA was descending through about 6,600 feet. At 2050:27, the SDNR controller again cleared N434PA to descend and maintain 5,200 feet. The pilot read back the clearance, and the SDNR controller then transmitted, "Seminole four three four papa alpha is five miles from escon. Cross escon three thousand five hundred or above cleared ILS 24 at Palomar." The pilot of N434PA acknowledged.

At 2052, the controller-in-charge (CIC) of the area including the SDNR sector received a call from San Diego automated flight service station (AFSS) reporting that they were receiving a strong emergency locater transmitter (ELT) signal in the area of the Julian VOR. The AFSS specialist asked the CIC to have controllers check with aircraft in the area in order to begin localizing the source. The CIC contacted the controllers at both the San Diego West and North sectors to attempt to locate the ELT signal. At 2053:23, the SDNR controller transmitted, "Seminole four papa alpha can you uh come up on one two one point five and check for an ELT please?" There was no response. The SDNR controller then made two more attempts to contact N304PA without success. He then transmitted, "Seminole four three four papa alpha how do you hear?" The pilot of N434PA replied, "four three four papa alpha five by five." The SDNR controller then instructed the pilot of N434PA to contact Palomar tower, and the pilot acknowledged.

Between 2054:21 and 2055:36, the SDNR controller made five more unsuccessful attempts to contact N304PA. At 2058:34, the pilot of N6ZP asked, "SoCal six zulu papa just for my own heart did you get a hold of that Seminole?" The SDNR controller responded, "No uh we're checking right now uh I don't uh we don't know where it is right now uh last we saw of him he was just five southeast of Julian same route that you were four papa alpha."

There was no further contact with N304PA.

1.5 Personnel information

1.5.1 Flightcrew

The occupants consisted of two private pilots, both with recently acquired instrument and multi-engine ratings. The intension of the flight was to build flight experience. The normal practice at the academy was for one pilot to be pilot-in-command on the outbound leg and the other pilot to be the pilot-in-command on the return leg of the trip.

A review of Federal Aviation Administration (FAA) airman records, Okalahoma City, Okalahoma, revealed the occupant-1 held a private pilot certificate issued on April 12, 2004, with ratings for single-engine land, multi-engine land, and instrument ratings for airplanes. Occupant-1 held a first-class medical certificate issued on July 10, 2003, with the restriction that he must wear corrective lenses. Occupant-2 held a private pilot certificate issued on April 30, 2004, with ratings for single-engine land, multi-engine land, and instrument ratings for airplanes. Occupant-2 held a first class medical certificate issued on November 18, 2003, with the limitation of wearing corrective lenses for distant vision.

Occupant-1's flight logbook was not recovered or examined by the Safety Board investigator. Occupant-1's accumulated flight time was calculated from flight and training records provided by Pan Am International Flight Academy, which may not be all inclusive of his flight experience. The Pan Am International Flight Academy records revealed that the pilot had approximately 174.8 total hours of flight time with 21.6 hours of that in multi-engine aircraft. He had approximately 46.8 hours of simulated instrument time in an airplane and 12.2 hours of night flying.

Examination of occupant-2's flight logbook revealed he had 239.8 hours of total flight time, 51.3 hours of multi-engine time, 50.4 hours of simulated instrument time in an airplane, and 37.2 hours of night flying.

1.5.2 ATC Controllers

The Safety Board ATC Group Chairman conducted detailed controller interviews, which are described in the ATC Group Factual Report section in the Official Docket of this accident. The San Diego North Radar Controller was certified in this position in October 1975. The San Diego Area Controller-in-Charge was certified in this position in March 1992. The San Diego North Radar Handoff Controller was certified in this position in February 1999. The San Diego Area Supervisor West Radar Controller became supervisor in 1999 and is qualified in the North, West, and South Bay sectors. The Los Angeles Sector 9 Radar Controller has been certified in this position since January 2003. Los Angeles Area E Controller-in-Charge has been certified in this position since April 1989.

1.6 Aircraft information

The airplane was a Piper PA-44-180, serial number 4496123, which was a twin engine, four seat, equipped aircraft. The airplane was powered by two Lycoming O-360 engines with Hartzell propellers. Examination of the engine and airframe maintenance logbooks revealed a total airframe and engine time of 2,467.8 hours when it underwent its last maintenance inspection on May 4, 2004. The airplanes maintenance was conducted under the direction of the Pan Am International Flight Academy's Progressive Inspection Program. The airplanes flight record log revealed that the airplane had accumulated 17 hours of hobbs time since May 4th.

The airplanes flight record log that is kept with the airplane has entries for both occupants, with occupant-1 listed first with the "flight hobbs out" field entered as 3129.5, the "flight hobbs in" field blank,

Aircraft

Registration
N304PA
Reported as
Piper PA-44-180
Category
Airplane
Serial number
4496123
Airframe hours
2,468
Engines
Lycoming O-360-A1h6, 180 horsepower, reciprocatingLycoming LO-360-A1H6, reciprocating
Damage
Destroyed
Flight
Personal · Part 91
Operator
Pan Am International Flight Academy
Registered owner
Merrill Lynch Business Financail Services
Airworthiness certificate
Standard, Normal
Last inspection
Continuous airworthiness · May 4, 2004 · 17 hours before
Departed
KDVT · Phoenix, AZ
Destination
KCRQ · Palomar, CA
Flight plan
IFR
Airport
KCRQ · McClellan-Palomar

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
20
Injuries
Fatal
Certificate
Private
Airplane ratings
Single-engine land, Multi-engine land
Instrument ratings
Airplane
Medical
Class 1, Valid Medical--w/ waivers/lim
Last flight review
April 25, 2004
Toxicology
Performed
Flight hours
175 total · 22 in this make and model · 94 as pilot in command · 67 in the last 90 days · 13 in the last 30 days
Role
Co-pilot
Age
24
Injuries
Fatal
Certificate
Private
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane
Medical
Class 1, Valid Medical--w/ waivers/lim
Last flight review
April 30, 2004
Toxicology
Performed
Flight hours
240 total · 51 in this make and model · 111 as pilot in command · 53 in the last 90 days · 0 in the last 30 days

Weather

Conditions
Visual (VMC) · Night/dark
Wind
180° at 4 knots
Visibility
10 statute miles
Lowest ceiling
2,000 ft overcast
Temperature
59 °F, dew point 50 °F
Altimeter
29.87 inHg
Observed at
KRMN, 18 nm away

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.