Sunday, September 06, 2015

Government probes further into incident at Ha’apai airport

An incident that almost claimed the lives of passengers on board a Real Tonga Airline flight at Ha'apai airport was told that pilot and assistant pilot had differences in interpretation of the aircraft airspeed indicator last Monday.

The Hon. Minister of Infrastructure and Tourism ‘Etuate Lavulavu reported the latest report from the airline in Parliament on Thursday.

He said the airspeed indicator instrument in front of the pilot indicated it’s time for the plane to take off yet the co-pilot’s same instrument indicated otherwise. Their differences caused the plane to swerve to the side before it came to an abrupt halt and almost hit the fence at the airport.

The airspeed indicator is an instrument used to display the craft's airspeed in order to maintain airspeed specific to the aircraft type and operating conditions.

It was reported in Parliament after much concern raised by Ha’apai 13 MP Veivosa Taka that the incident almost claimed the lives of passengers on board the Real Tonga Airline’s flight last week.

Taka claimed one of the passengers on board that flight Dr. Mohenoa Puloka said it was a terrifying moment to see the plane landed only 20 feet away of Koulo’s cliff.

Lavulavu informed Parliament on Thursday that investigation is underway to ensure it’s not happening again. He said that Cabinet has also requested assistance from Pacific Aviation Safety Office (PASO) in probing further into the matter.

He also denied Taka’s curiosity the pilots were intoxicated for mishandling errors of the airspeed indicator reading.

Earlier, when the incident was raised in Parliament, it prompted an uproar from Vava’u number 2 Noble Representative Lord Tu’ilakepa who called for immediate suspension of all Real Tonga Airlines' flights.

He claimed it was a serious matter that Government must act promptly to avoid further aviation accident from happening. Tu’ilakepa said Government should use their conscience in dealing with the issue. He also gave reference to an incident where an Israel’s plane urgently requested landing rights in Tonga yet it was a Sunday.

Tu’ilakepa said God gifted man with sound mind to make the right decision and that was exactly what the previous Government did.

“Government at the time put aside the laws and use their conscience and sound mind to do what was right back then,” explained Lord Tu’ilakepa.

‘Eua Noble Representative Lord Nuku was also concerned with confirmation the same aircraft that almost had an accident in Ha’apai is still flying.

In response Government said it has no authority to immediately suspend flights of Real Tonga Airlines since there are due process it must adhere to before making and decision. First a report must be submitted from the airline and further investigation will be carried out before the Government makes the final decision.

Cabinet was also concerned with whoever responsible for issuing the direction for the aircraft to fly, especially it was a really bad weather last Monday (August 24).

Lavulavu said the Government was taking the matter seriously for the safety of people and also because it is an ongoing problem.

“One incident involved a Real Tonga’s flight crashed landing at ‘Eua airport and punctured one of its tire. Another incident involved a brake failure of Real Tonga’s 12-Harbin Y12 aircraft that caused the aircraft to veer on the runway. And the latest report from Ha’apai is a concern,” said Lavulavu.

He added the reported incident at Ha’apai also questioned the potential management of local domestic operator to provide continuous air service domestically.

Lavulavu said that’s always Government’s initiative when seeking assistance from overseas to ensure reliable and people safety air services.

Vava’u Number 2 Noble Representative Lord Tu’ilakepa also argued it is the Government’s responsibility to check the airworthiness of Real Tonga’s aircraft, check the actions of pilots and suspend all its flights. He also asserted MPs that the Government should use their conscience in dealing with the matter and not wait for death to come and then further action.

Vava’u 15 constituency MP, Samiu Vaipulu moved the Government’s decision and called on Cabinet to get an independent audit check of the aircraft for air safety procedures.

Meanwhile Ha’apai 13 MP said Dr. Puloka maintained their safety is not because of the pilot’s expertise but it’s God’s love.

“He hears our cries and prayers during our ordeal,” explained Dr. Puloka.

Puloka called for immediate Government action in addressing the problem to avoid further mishap from happening.

When Real Tonga Airlines was issued with the required certification to operate domestically in Tonga they pledged a reliability and people safety as their top priority.

Original article can be found here: http://parliament.gov.to

Lynchburg City Council to consider long-term lease for aeronautic services at Lynchburg Regional Airport (KLYH), Virginia

After a protracted negotiation process, Lynchburg City Council is set to consider and potentially authorize a long-term lease agreement with Aviation Resources Inc., a fixed-base operator at Lynchburg Regional Airport.

Fixed-base operators provide fueling and other aeronautic services. Those services at Lynchburg Regional Airport previously were provided by two FBOs, Freedom Aviation and Virginia Aviation.

In 2014, Freedom Aviation LLC purchased Virginia Aviation. Virginia Aviation’s agreement with the city did not allow the lease to be sold or transferred to another party, and a provision stated the lease would be terminated if Virginia Aviation was sold.

The Lynchburg Regional Airport Commission recommended the city operate its own limited FBO, but City Council voted in February to allow the negotiation for a long-term lease with Freedom Aviation.

All three entities are related; Aviation Resources is doing business as Virginia Aviation, and Virginia Aviation is owned by Freedom Aviation, Airport Director Mark Courtney explained in an interview. Freedom Aviation is a subsidiary of Liberty University.

The final draft lease agreement to be presented to City Council on Tuesday will be for a term of three years with the option to renew for terms of five years. Aviation Resources will pay the city nearly $17,000 a month to rent facilities at the airport, but the agreement states rent may be lowered if Aviation Resources’ financial statements show no net profit. Rent may not be lowered below $11,361 per month, the draft lease agreement states.

Aviation Resources may not be able to “assign, sell or transfer,” the lease without the city’s approval, although there is the possibility of subleases under specified conditions.

At the Tuesday meeting, City Council also will consider an amendment to a franchise agreement with Freedom Aviation LLC, which formerly went by the name Falwell Aviation Inc., that would remove a restriction prohibiting the company from performing fueling of commercial and military aircraft.

City Council will meet Tuesday at 7:30 p.m. in City Hall.

Source:  http://www.newsadvance.com

Aer Lingus chairman leases aircraft to potential rival • Fly Leasing supplies jet to Norwegian airline trying to set up long-haul service in Republic

Aer Lingus chairman Colm Barrington’s Fly Leasing recently supplied a Boeing aircraft to Norwegian Air, the Scandinavian operator that is attempting to set up a budget long-haul airline in the Republic.

Mr Barrington is chief executive of DĂșn Laoghaire-based Fly Leasing, one of a number of Irish companies that finance and supply aircraft to airlines around the world.

Documents recently filed with the Companies Registration Office (CRO) by Norwegian Air International, an Irish-registered subsidiary of Norwegian Air Shuttle, show Fly leased a Boeing 737-800 to the company earlier this year.

The deal with Fly is one of a number agreed by Norwegian Air International with suppliers this year, all of them for Boeing 737-800s, a short- to medium-range craft used by a large number of carriers, including Ryanair.

The Scandinavian airline is leasing the craft. The lessors use the aircraft as security for the rent, which is why the agreement is registered with the CRO.

Most airlines lease some or all of their craft. Leasing companies buy the aircraft using a combination of their own and borrowed cash and rent them to the carriers. Alternatively they buy the craft from the airlines and lease them back.

The Republic is a recognised hub for aircraft leasing, with most of the big players based here.

The Boeing 737-800 has a list price of €70 million but manufacturers generally give buyers discounts, particularly if they are buying large numbers or if they have an existing relationship.

Mr Barrington said this month Fly is on track to spend $750 million (€672 million) on new aircraft this year. His company recently sold a large number of mid-aged craft and is gearing up to replace these. It also completed a sale-and- leaseback deal for a 737-800 with an unnamed airline.

Norwegian Air International plans to establish a low-cost, long-haul business from the Republic that will offer flights between Europe and the United States and Far East for as little as €315 return.

The Irish Aviation Authority and Commission for Aviation last year granted the company the licences it needs to operate an airline from the State. However, its plans have met opposition in the US.

Its parent group’s chief executive, Bjorn Kjos, said last year Norwegian Air Shuttle intended to do much of its financing and leasing from the Republic. At that point, Irish entities owned half its 90 aircraft.

Accounts lodged by Norwegian Air International – the Irish-registered company – show it turned over $100 million in 2014, $49 million coming from supplying craft and crew to operate its parent’s Scandinavia-Bangkok routes, $40 million from ticket sale and the balance came from “other revenues”.

The figures show it lost almost $100 million. Much of this was down to an $88 million write-off stemming from its purchase of the business run by a subsidiary, Norwegian Assets Ltd, which was subsequently liquidated.

Original article can be found here: http://www.irishtimes.com

Despite smaller plane, passenger numbers rise at Columbia Regional Airport (KCOU), Missouri

COLUMBIA - Officials shared new statistics Saturday showing passenger numbers on the rise at Columbia Regional Airport (COU).

Greg Cecil with the airport advisory board said the number of passengers getting on a flight at COU is up 20 percent from 2014, while the number of people getting off a flight at the airport is up 22 percent.

Cecil said the increase is largely due to a larger plane being used on the flight from Columbia to Chicago.

"There's huge demand here," Cecil said.

The larger aircraft, the CRJ-700, seats roughly 15 more passengers than the smaller ERJ-145, which was previously used on the route. The CRJ was also used to fly to Dallas, but the regional carrier that operates flights out of COU for American Airlines, quickly brought back the smaller jet, Cecil said.

"Airlines are constantly changing how they do business," he said. "Also, there could be a shift from time to time in the regional airline that is the code share partner for American Airlines."

American, like most major U.S. airlines, subcontracts its shorter-haul regional flights to smaller regional carriers, which operate smaller jets on behalf of American.

The change back to the 50-passenger ERJ was partly due to a lack of service facilities for the larger plane in Dallas.

"It's my understanding that there was not a service hanger for the -700s in Dallas and so there were for the 50 passengers that they're using now" Cecil said. "A lot of those things we have no control over because the airlines are shifting aircraft around to where it makes more sense for them to make a profit."

While the numbers discussed Saturday were a good sign of growth, Cecil said any further expansion of the airport is a slow process.

"Right now we're bursting at the seams on our terminal, and so while, you know, we'd love to have a plane that would accommodate 150 people, if we had two planes that were capable of doing that and we could fill them, we'd have some real issues in the current terminal" He said.

Cecil said he hopes the airport can continue moving forward with expansion plans, and said a flight to Charlotte has been the topic of heavy conversation.

"It's in our demand analysis that that would make sense to go there. But a lot of it's just a matter of time and us being able to accommodate," He said.

Cecil said crews could have a plan for a new or renovated terminal within the year.

Story, video and comments:   http://www1.komu.com

Controlled Flight into Terrain (CFIT): Cessna 310H, N1099Q; fatal accident occurred September 05, 2015 in Silverton, Colorado






Aviation Accident Final Report - National Transportation Safety Board

Investigator In Charge (IIC): Gallo, Mitchell

The National Transportation Safety Board traveled to the scene of this accident.

Additional Participating Entities:

Federal Aviation Administration / Flight Standards District Office; Salt Lake City, Utah
Textron Aviation; Wichita, Kansas
Continental Motors; Mobile, Alabama 

Investigation Docket - National Transportation Safety Board:


NTSB Identification: CEN15FA400
14 CFR Part 91: General Aviation
Accident occurred Saturday, September 05, 2015 in Silverton, CO
Probable Cause Approval Date: 04/19/2017
Aircraft: CESSNA 310H, registration: N1099Q
Injuries: 4 Fatal.

NTSB investigators either traveled in support of this investigation or conducted a significant amount of investigative work without any travel, and used data obtained from various sources to prepare this aircraft accident report.

The airplane owner, who was a noninstrument-rated private pilot and did not hold a multiengine airplane rating, was conducting a visual flight rules (VFR), personal cross-county flight in the multiengine airplane. Before the accident flight, the pilot flew the airplane to an intermediate airport to refuel. A review of air traffic control (ATC) radio transmissions between the pilot and an air traffic controller between 0911 and 0938 showed that, during the approach for landing, the pilot misidentified in every transmission the make and model airplane he was flying, referring to his airplane as a Piper Comanche instead of a Cessna 310. Further, he did not provide correct responses to the controller's instructions (for example, he reported he was set up for the left base leg instead of right base leg as instructed), and he provided inaccurate information about the airplane's position, including its distance and direction from the airport. 

A witness stated that, after the airplane landed and while it was taxiing, it almost hit another airplane and golf carts, and it was taxied close enough to the fuel pumps that it "knocked" a ladder with one of its propellers. The witness said that the pilot was not "observant about his surroundings." While at the intermediate airport, the pilot requested an abbreviated weather briefing for a VFR flight from that airport to the destination airport. However, the pilot incorrectly identified the destination airport as "L51," which was depicted on the VFR sectional chart for the Amarillo area but referred to the maximum runway length available at the destination airport not the airport itself. L51 was an airport identifier assigned to an airport in another state and located north of the accident location and in a direction consistent with the airplane's direction of travel at the time of the acident. 

During the departure for the accident flight, the pilot taxied to and attempted to take off from an active runway without any radio communications with or clearance from ATC, which resulted in a runway incursion of an air carrier flight on final approach for landing to the runway. The air carrier initiated a missed approach and landed without further incident. The controller reported that the runway incursion was due to the accident pilot's loss of "situational awareness." Radar data showed that, after the airplane departed, it turned northward and away from a course to the intended destination airport. The northward turn and track was consistent with a course to an airport in another state. According to meteorological information, as the flight progressed northward, it likely encountered instrument meteorological conditions (IMC) while flying into rain showers. The wreckage was found in rising mountainous terrain, and the accident wreckage distribution was consistent with a low-angle, high-speed impact. Given that postaccident examination of the airplane revealed no mechanical anomalies that would have precluded normal operation, it is likely that the noninstrument-rated pilot did not see the rising mountainous terrain given the IMC and flew directly into it. 

The pilot had told person(s) that he flew F-4 Phantoms, but a military identification card showed that the pilot was a retired Marine lance corporal. Although the pilot's logbook showed that he had accumulated 150 hours of multiengine airplane flight time, there was no record of the actual flights showing the accumulation of 150 multiengine airplane hours or any record that he had flown military aircraft. The logbook did not show that the pilot had received any flight training in the accident airplane. The logbooks also showed that he had flown numerous flights in the airplane with passengers without proper certification and that he had not had a recent flight review as required by Federal Aviation Regulations (FARs). The pilot's logbook showed that he had once made low-altitude (10 ft above the ground) passes over a parade in the same airplane. The airplane had not received an annual inspection for continued airworthiness as required by FARs. The pilot's noncompliance with FARs and the logbook entries indicate that he had a history of poor decision-making and piloting errors, which was reflected in his behavior and actions while landing at the intermediate airport and during the taxi and takeoff phases of the accident flight. 

Although the pilot had a number of medical problems that potentially could have interfered with his ability to safely operate the airplane, including spinal cord injuries, diabetes, and psychiatric issues, and was taking medications to treat them, these conditions and medications likely would not have interfered with his navigational skills and his ability to communicate on the radio or affected his decision-making. Although the available medical information was limited by the degree of damage to the body, there was no evidence of a medical condition or effects of a medication that contributed to this accident. Although ethanol was detected in the pilot's tissues, it likely resulted from postmortem production.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The noninstrument-rated pilot's improper judgment and his failure to maintain situational awareness, which resulted in the flight's encounter with instrument meteorological conditions and controlled flight into terrain during cruise flight.

Members of the San Juan County and La Plata County search and rescue teams at the scene of the plane crash on September 7th, 2015. The Colorado Air National Guard helicopter that airlifted them to the remote location is in the background.

HISTORY OF FLIGHT

On September 5, 2015, about 1408 mountain daylight time a Cessna 310H, N1099Q, impacted mountainous terrain near Silverton, Colorado. The private pilot, a pilot-rated passenger, and two passengers were fatally injured. The airplane was destroyed by impact forces. The airplane was registered to and operated by the pilot as a 14 Code of Federal Regulations Part 91 a personal flight. Instrument meteorological conditions (IMC) prevailed at the time of the accident, and no flight plan had been filed. The pilot was not using air traffic control (ATC) services. The flight departed from Flagstaff Pulliam Airport (FLG), Flagstaff, Arizona, about 1150 and was destined for Tradewind Airport (TDW), Amarillo, Texas.

A fuel receipt from the Big Bear City Airport (L35), Big Bear, California, showed that 20.04 gallons of fuel was purchased for the airplane on September 4, 2015.

The pilot's daughter stated that the airplane was kept at L35 during the summer and afterward at Barstow-Daggett Airport (DAG), Daggett, California. She said that her father departed from L35 on September 5, 2015, about 0615 PDT, and arrived at DAG about 0630 PDT to pick up the passengers. He was then going to fly to Amarillo, Texas, following Interstate 40, where they were going to have dinner and then return the same day. She said that her father did not call her after he refueled and departed Flagstaff and that she called for help on September 6 because she had not heard from him. She said that there was another pilot aboard and that they had a GPS. She said that her father did not know anyone in Colorado or Montana.

A part-time Unicom operator at L35 said that the pilot talked about conducting the flight about 1 week before the accident. The pilot asked "a lot of different pilots to go along as copilot" and asked him to go on the flight. The Unicom operator did not know what time the pilot departed on September 5, but "it was pretty early in the morning" when the pilot left to pick up passengers. The Unicom operator stated that the pilot purchased the airplane "not too long ago," that the airplane radios were "very old," and that the "instruments were not all that good." 

The pilot's initial contact with an air traffic control (ATC) facility on the day of the accident occurred during a visual approach to FLG. A rerecording of provided radio transmissions between the pilot and an FLG air traffic controller between 1011 and 1038 follows:

N1099Q: "Flagstaff traffic this is Piper Comanche N1099Z I'm sorry quebec we're approximately thirty miles miles west of the field anybody know what how the weather is down there you socked in there cause we are flying over the top here."

FLG tower: "Comanche 1099Q flagstaff tower we are open. The uh the ATIS is also broadcasting we're 900 broken, 1,600 broken, 2,400 overcast, visibility 10." 

N1099Q: "Oh thank you I just turned the ATIS then. I appreciate it thank you Flagstaff."

N1099Q: "Flagstaff tower 1099Q about to land we are we are approximately 10 miles west of the airport." 

FLG tower: "Comanche uh 99Q flagstaff tower the uh we're IFR at the airport 900 broken 1600 broken visibility 10."

1099Q: "We are now approximately 8,000 feet we have visibility looks like greater than 10 miles." 

FLG tower: "Comanche 99Q I concur with the visibility uh are you requesting something special."

FLG tower: "Comanche 99Q the field is now VFR the uh ceiling is well I have a scattered layer of 1,200 ceiling 1,600 report a right base for runway 21."

N1099Q: "Report right base for runway 21 will do quebec."

FLG tower: "Comanche 99Q uh verify you have information charlie."

N1099Q: "Copy that we have we got a little bit of a … here."

FLG tower: "Comanche 99Q roger the wind is 220 at 8 temperature 16 density altitude is 8,400 dew point 13 and the altimeter 30.26."

N1099Q: "30.36 thank you."

FLG tower: "altimeter 30.26 26."

N1099Q: "Flagstaff tower this is quebec were gonna report left base runway 21 I just want to confirm that quebec."

FLG tower: "Comanche 99Q are you set up for a right base or a left base you're coming from the west you said."

N1099Q: "Oh its showing left base on my uh GPS left traffic on runway 21."

FLG tower: "Comanche 99Q uh we can make whichever way you want I just need to know which direction you're coming from."

N1099: "Well we're comin we're we're coming from 270 right now." 

FLG tower: "From 270 you should be west of the…airport where was the destination you left from."

N1099Q: "Well we can report let's see the winds are from uh what."

FLG tower: "Comanche 99Q the wind is 240 at 6 just report base."

N1099Q: "Well… we're…right now…"

FLG tower: "Comanche 99Q that came in broken and unreliable."

N1099Q: "The winds are 210."

FLG tower: "Wind 210 at 8."

FLG tower: "Comanche 99Q how far from the airport are you."

N1099Q: "We're downwind 21 left we're settin up for uh base for 21 left."

FLG tower: "Okay we only have runway 21 okay I see you now you are on a left downwind runway 21 cleared to land wind 210 at 8."

FLG tower: "Comanche 99Q runway 21 cleared to land."

N1099Q: "…the end of the runway now…on the downwind we'll make base to final."

FLG tower: "Comanche 99Q runway 21 cleared to land."

N1099Q: "Cleared to land runway 21."

FLG tower: "N99Q are you going to uh wiseman aviation the FBO."

N1099Q: "Yes we want to gas up can we exit."

FLG tower: "N99Q continue on the runway turn right alpha seven self-serve fuel will be towards the base of the rotating beacon if you want the uh FBO it's a green building near the uh rotating beacon."

N1099Q: "Okay I see the rotating beacon I guess we can make a right taxi here."

FLG tower: "N99Q you make right turn alpha seven that will get you more direct."

N1099Q: "Gotcha alpha seven."

N1099Q: "Flagstaff…down and clear of runway taxi to fuel pump."

N1099Q: "Yep."

N1099Q: "Quebec gettin ready to touchdown here runway 21 here flagstaff."

A fixed-base operator (FBO) employee at FLG stated that, during the airplane's taxi to the fuel pumps, the airplane almost hit an "Eclipse jet," and he thought it was going to hit golf carts that were near the FBO building. When the airplane arrived, it taxied close enough to the self-serve fuel pumps that it "knocked" a ladder with one of its propellers. He said that the pilot was not "observant about his surroundings." The airplane had white "house letters" painted on its side similar to those on fighter or Air Force aircraft. The house letters had "pilot" followed by a name, which he could not remember seeing, and "copilot" followed by "God." The airplane "looked clean.". The employee stated that the pilot told him that he hoped there were no more clouds, there was no more weather, and that he wanted 75 gallons of fuel for the airplane. The pilot pointed east and added that it should be 2 more hours to their destination. The employee thought the destination was Amarillo but was certain that it was in Texas.

The FBO employee said he showed the pilot how to use the fuel pump. The pilot gave the fuel order and payed for the fuel with cash. A passenger helped fuel the airplane at the self-serve fuel pump; he added about 15 gallons of fuel to the left and right wing fuel tanks (auxiliary fuel tanks) and put the fuel caps back on. The wing tip fuel tanks (main fuel tanks) were topped off. 

The FBO employee stated that another passenger said that he bought a "brand new GPS" and could not get "ADAS[Automated Weather Observing System Data Acquisition System]" to work and thought he also said, "oh well we'll figure it out later."

At 1054, the pilot called Lockheed Martin Flight Services (LMFS) while at FLG and requested an abbreviated weather briefing for a visual flight rules flight from FLG to Amarillo, Texas. The pilot told the weather briefer that the Amarillo, Texas, airport identifier was "L51"; this was not the correct identifier for Tradewind Airport. The correct identifier was TDW; the L51 airport identifier was assigned to Heller Farm Airport, Winifred, Montana. Despite providing the weather briefer with the wrong airport identifier, the briefer did provide information for the flight to Amarillo. The pilot received the latest weather information in the briefing, which included Airmen's Meteorological Information for mountain obscuration, convective outlooks (the briefer mentioned that there was no convective activity yet but told the pilot to stay updated via Flight Watch), the terminal aerodrome forecast for Rick Husband Amarillo International Airport, Amarillo, Texas, the Meteorological Terminal Aviation Routine Weather Report for Tucumcari Municipal Airport, Tucumcari, New Mexico, and the winds aloft at 9,000 and 12,000 ft between the departure and destination airports. No record was found indicating that the accident pilot received or retrieved any other weather information before or during the flight.

The FBO employee at FLG stated that, after the airplane was fueled, it taxied past the FLG ATC tower without making any radio communications with ATC. The airplane taxied onto a runway while an "air shuttle" was landing, and the air shuttle (SkyWest 2992) had to abort its landing. The pilot then turned the radio on and taxied off the runway and onto a taxiway near the air carrier ramp. A FLG airport rescue and firefighting (ARFF) employee drove to the airplane to talk to the pilot. The ARFF personnel told the left front pilot seat occupant that he had to move the airplane because it was blocking an air carrier ramp entrance. The employee said that FLG ATC had a "lengthy conversation" with the pilot after he had taxied the airplane off the runway and was told to call the FLG ATC tower. The employee said that he overheard on the FLG ATC frequency the air shuttle pilot asking about the airplane, and FLG ATC responded by saying it was "a case of situational awareness."

According to an Air Traffic Mandatory Occurrence Report, SkyWest 2992, CRJ2/L, was on the instrument landing system (ILS) runway 21 approach and was cleared to land on runway 21. The accident airplane was observed northbound on taxiway A without authorization from the FLG tower. N1099Q turned right onto the connecting taxiway A2 continuing toward runway 21. At that time, the tower controller issued go-around instructions to SkyWest 2992 on about 1 1/2 mile final and coordinated missed approach instructions with Phoenix Approach. The accident airplane continued onto runway 21 and initiated the takeoff roll and then established communication with the tower. The tower controller instructed the accident pilot to cancel takeoff and exit the runway. SkyWest 2992 was vectored back to the ILS approach course and landed without further incident.

The FLG ATC tower controller stated that, during his telephone conversation with the accident pilot following the runway incursion, the pilot "kind of missed the point," "came up with excuses" for the runway incursion, and did not know there was another airplane "out there" during the runway incursion. The controller stated that, when he told the pilot that there was an airliner on final, and it was at that point that the pilot "realized the gravity of the situation." The pilot then said that he had been flying for 50 years and nothing like this happened before. The controller said it "seemed" that the pilot "really didn't register" what had happened. The controller added that he did not remember having to repeat questions that he asked the pilot. The pilot did not seem upset nor did the pilot ask questions in response to the questions asked by the controller. The controller said that, during the second takeoff attempt, the accident airplane settled onto the runway after it had lifted off and then climbed out with a left turn.

The ARFF employee stated that the accident airplane taxied from the FBO to taxiway A2, held at A2, and then taxied onto an active runway with a commercial regional airplane on short final without any radio contact to ATC. The employee said that the accident pilot transmitted that he did not have the airplane's radio turned on or "something to that effect" and stated that they were going to take off. The employee said that the radio transmissions from the accident pilot were "screwy" and "lacked organization and context, and was not current."The employee said that it seemed like the pilot had spent a lot of time around uncontrolled airports. The employee said that during the airplane's second takeoff attempt, the airplane remained low over runway 21 for a long time and that, about 1,000 ft from the departure end of the runway, the airplane pulled up, "not steep," and entered a left turn to the east and headed northeast.

The flight was not receiving ATC services and was not assigned a transponder squawk code. The airplane used a squawk code of 1200 based upon ATC recordings and the arrival/departure times to and from FLG. The radar track of an airplane with a squawk code correlating to those times was plotted to provide an overview of the flight and is shown in figure 1.

Figure 1. A radar plot of an airplane flight track consistent with the accident airplane. The plot shows a turn toward the north. 

PERSONNEL INFORMATION

Pilot/Airplane Owner Information

The pilot, age 71, held a private pilot certificate with a single-engine land airplane rating. The pilot's most recent FAA third-class airman medical certificate was issued December 17, 2013, with the limitation that he must wear corrective lenses for near and distant vision. At that time, the pilot reported a total flight time of 1,000 hours, 200 hours of which were in last 6 months. There was no military record received showing that the pilot had any flight experience in military airplanes.

The pilot's daughter stated that her father flew F-4 Phantoms. An L35 employee reported that he believed that the pilot said he flew F-4 Phantoms in the military and transitioned to helicopters and was injured in Vietnam. A Department of Defense (DOD)/Uniformed Services identification card that belonged to the pilot was recovered from the accident site. The card showed that he served in the US Marine Corps at grade "E3," which according to DOD's Enlisted Rank Insignias was a grade of Lance Corporal.

The L35 employee said the pilot told him the he was a doctor and "had an MD." He stated that he researched the things told to him by the pilot, and none of it was true. He said the pilot had "some speech issues" and that he had a "high pitched garbled voice." He said that pilot could not "keep a fluent conversation" without having an "issue with talking." He said that the pilot's aircraft radio transmissions were "very short," which "concerned" him and L35 staff. He said "there were a lot of circumstances that concerned people about his [the pilot's] flying."

A review of the pilot's FAA airman record revealed that, on July 18, 2009, the pilot failed the practical portion of the examination in his first attempt for a private pilot certificate with a single-engine land airplane rating. Upon reexamination for the certificate/rating, he was to be reexamined on the following: IX. Basic Instrument Maneuvers, V. Performance Maneuver, and VII. Navigation. At the time of the examination, the pilot reported a total time of 301 hours and a total instruction time received of 52 hours. On September 21, 2009, the pilot successfully passed his second attempt and was issued a private pilot certificate with a single-engine land rating. At the time of reexamination, the pilot reported a total time of 305 hours and a total instruction time received of 55 hours. No record was found indicating that the pilot had been issued a multiengine airplane rating or that he had flown military aircraft..

The pilot's logbook, which was recovered from the accident site by first responders, had flight entries beginning July 7, 2007, and ending August 15, 2015. The logbook showed that the pilot's total flight time in single and multiengine airplanes was 801.9 hours, 255.6 hours of which were in single-engine airplanes and 217.7 hours of which were in multiengine airplanes. The first logbook page entry of a multiengine airplane flight time was dated January 6, 2013, in a Piper PA-23-250, N54155 and it showed a total multiengine flight time of 10.5 hours. The page also showed that the pilot's a total multiengine flight time for previous flights was 150 hours; however, there were no logbook entries documenting flights in multiengine airplanes before the page indicating that he had 150 hours of multiengine flight time. The pilot's logbook showed a total flight time in night conditions of 17.0 hours, of 0.2 hour of which was in the accident airplane. The most recent flight entry in night conditions was dated December 2, 2014, in the accident airplane for 0.1 hour. 

The accident airplane's Application for Registration to the pilot was dated June 27, 2014. The Aircraft Bill of Sale shows the airplane title was transferred to the pilot on July 2, 2014, from Aerobanc of America, Inc. The first flight entry in the pilot's logbook for the airplane was dated July 3, 2014. No record was found indicating that the pilot had received training in the airplane after its purchase/registration. The pilot's logbook contained a total of 72 flight entries for the airplane with a total flight time of 35.4 hours. During this period, the logbook's remarks sections had entries that showed the pilot had flown with passengers. There was one logbook entry dated March 7, 2015, for a flight in the airplane that had the following remark: "I let [name of pilot-rated passenger] fly part way back."

A logbook entry showed that the pilot's most recent flight review, as required by Part 61.56, was dated July 17, 2013, with a departure and destination of Apple Valley Airport, Apple Valley, California. The flight was in a Piper PA-28-180 with a flight time of 1.0 hour, a ground instruction time of 1.0 hour, and the remarks, "FAR 61.56 FLT. REVIEW VFR PROCEDURES." The flight review was conducted by the same flight instructor that had provided the pilot-rated passenger's flight review. Title 14 CFR Section 61.56(c) stated that a flight review must have been accomplished within the 24 calendar months preceding the month in which a pilot acts as pilot-in-command in an aircraft for which that pilot is rated. The pilot was overdue for his flight review by about 2 months.

A logbook entry dated July 4, 2012, showed a flight from DAG to DAG in a Piper PA-28-180 that was 1.0 hours in duration. The remarks section for the flight had the following entry: "Flew over parade 10 feet off ground made six passes." A logbook entry dated July 4, 2013, showed a flight from DAG to DAG in a Piper PA-28-180 that was 2.0 hour long. The remarks section for the flight had the following entry: "Landed on Rt. 66 4 July Parade. With Mayor." A logbook entry dated November 2, 2013, showed a flight from DAG to "Rt.66," in a Piper PA-28-180 that was 0.2 hour long. The remarks section for the flight had the following entry: "Flew to the barn landed on RT. 66 for auto show." According to 14 CFR 91.119, "Minimum safe altitudes," a pilot should not operate an aircraft at an altitude of 500 feet above the surface, except over open water or sparsely populated areas. In those cases, the aircraft may not be operated closer than 500 feet to any person, vessel, vehicle, or structure. 

A logbook entry dated June 14, 2014, showed a flight in a Piper PA-28-180 that was 2.0-hour long and included five landings from "DAG" to "Big Bear" with the remarks: "Young Eagles." Regarding this entry, the L35 employee reported that nothing at the time made him question the pilot's flying ability. He said the pilot wanted to fly in the Young Eagles program and that they have a large Young Eagles program at L35. He said that they had asked the pilot to produce the required paperwork for the Young Eagles program, but the pilot never produced the paperwork, so the program representative decided about 8 to 10 months before the accident to not allow the pilot to fly in the Young Eagles program.

A logbook entry dated August 15, 2015, showed a 0.3-hour-long flight in the accident airplane "L35" to "L35." The remarks section for the flight stated: "Big Bear airshow. made it. speed passes over runway." Regarding this entry, the L35 employee stated that there was "some issue" with the pilot during the Big Bear Airport air show. When the airport opened for departures, the pilot departed with passengers. Upon the pilot's return to the airport, he turned the airplane onto the final leg of the airport traffic pattern and did not have the airplane radio on. The shows's air boss cleared another airplane to depart from the active runway while the accident pilot was flying his airplane on short final. He stated that, instead of the pilot offsetting the airplane to the side of the runway during the go-around, the pilot performed a "low-level left turn over the crowd" with the landing gear and flaps extended. 

The pilot had no previous FAA record of accident(s), incidents(s), or enforcement(s) actions.A search of publically available information of airman certificate information from on the FAA's website, FAA.govGOV, using only the pilot/airplane owner's first and last name, revealed that the pilot/airplane owner only held a private pilot certificate with a single-engine land rating.

Pilot-Rated Passenger Information

The pilot-rated passenger, age 67, held a private pilot certificate with a single-engine land airplane rating. His most recent FAA third-class airman medical certificate was issued May 28, 2015, with the limitation that he must wear corrective lenses. At that time, he reported 1,000 hours of flight experience.

On March 25, 2003, the pilot-rated passenger successfully passed, on his first attempt, an examination for a private pilot certificate with a single-engine land airplane rating. At the time of examination the pilot-rated passenger reported a total time of 168 hours, and a total instruction time received of 90 hours.

The pilot-rated passenger's logbook, which was recovered from the accident site by first responders, had flight entries beginning February 26, 2009, and ending August 31, 2015. The logbook showed that his total flight time in all aircraft was 785.5 hours, all of which was in single-engine airplanes.

A logbook entry showed that the pilot-rated passenger's most recent flight review as required by Part 61.56 was dated June 11, 2015. The flight review was conducted by the same flight instructor who had provided the pilot's flight review.

The pilot-rated passenger's logbook showed a total flight time in night conditions of 17.0 hours. The most recent flight entry in night conditions was dated January 5, 2011. 

The pilot-rated passenger had no previous FAA record of accident(s), incident(s), or enforcement action(s).

AIRCRAFT INFORMATION

The accident airplane was a 1963 twin-engine Cessna 310H, serial number 310H-0099, airplane. It was powered by a Continental IO-470-VOCD, serial number 455693, engine and a Continental IO-470-D, serial number 79334, engine. The airplane was equipped with two 51-gallon capacity main fuel tanks and two 15.5-gallon capacity auxiliary fuel tanks. 

According to FAA airworthiness records, the most recent airworthiness certificate for the airplane was a Special Airworthiness Certificate dated April 11, 2006. The Special Airworthiness Certificate was a Special Flight Permit for the purpose of "Out of Annual Inspection – Maintenance." The airplane did not have a current airworthiness certificate at the time of the accident. A standard airworthiness certificate remains valid as long as the aircraft meets its approved type design, is in a condition for safe operation and maintenance, and preventative maintenance and alterations are performed in accordance with Parts 21, 43, and 91.

The pilot's daughter provided copies of the aircraft logbooks . These copies showed that the airplane's last annual inspection was dated May 1, 2014, at a Hobbs time of 1,541.3 hours and a total time in service of 5,367.3 hours.

Logbook entries annotated the left engine as serial number 455693 and the right engine as serial number 79334 and noted that the most recent annual inspections of the left and right engines were dated May 1, 2014. At the time of the inspections, the left engine had a time since major overhaul of 1,241.6 hours; the Hobbs time was not annotated. The right engine had a time since major overhaul of 858.4 hours and a Hobbs time of 1,541.3 hours.

Title 14 CFR 43.7 states that every airplane is required to undergo an annual inspection: "no person may operate an aircraft unless, within the preceding 12 calendar months, it has had an annual inspection and has been approved for return to service by a person authorized by Part 43.7."

METEOROLOGICAL INFORMATION

Astronomical Data

The astronomical data obtained from the United States Naval Observatory for the accident site on the day of the accident indicated that civil twilight began 0618, sunrise was 0645, sun transit was 1310, sunset was 1935, and civil twilight ended 2001.

Weather Information

Telluride Regional Airport (TEX), located 12 miles north-northwest of the accident site at an elevation of 9,070 ft mean sea level (msl) was the closest official weather station to the accident site. TEX had an Automated Weather Observing System, and its reports were not supplemented. 

At 1415, TEX reported wind from 190 degrees at 5 knots, 10 miles visibility, present weather thunderstorms in the vicinity, sky condition scattered clouds at 4,700 ft above ground level (agl), broken ceiling at 6,000 ft agl, broken skies at 7,000 ft agl, temperature of 17° C, dew point temperature of 7° C, and an altimeter setting of 30.34 inches of mercury. Remarks: automated station with a precipitation discriminator, lightning distant northwest, temperature 17.4° C, dew point temperature 6.6° C.

Closer to the accident site, observations from the nonofficial surface stations within 12 miles of the accident site reported gusting wind between 8 and 39 mph. The strongest wind was at the nonofficial surface stations closest to the accident site altitude and near the tops of the mountains between 10,000 and 12,000 ft. In addition, these stations reported rain showers in the vicinity and had relative humidity values greater than 80 percent around the accident time. These stations were above 10,000 ft, and the high relative humidity values were consistent with cloud cover at or above 10,000 ft and mountain obscuration due to clouds, precipitation, and mist. Figure 2 shows the three-dimensional Grand Junction, Colorado, weather surveillance radar-88 Doppler base reflectivity from the scan initiated at 1406 and the ATC Flight Track. 

Figure 2. Three-dimensional Grand Junction, Colorado, weather surveillance radar-88 Doppler base reflectivity from the scan initiated at 1406 and the ATC Flight Track. Blue and green colored areas depict reflectivity of greater than 10 decibels (dBZ) and greater than 20 dBZ, respectively.

AIRPORT INFORMATION

TDW was located about 482.7 nautical miles on a true course of 087° from FLG. The VFR sectional chart for the Amarillo area, shown in figure 3, depicted an airport identifier of TDW, not L51 as stated by the pilot, next to the airport name. L51 is shown once, but it referred to the maximum runway length available at TDW, which was 5,100 ft.

Figure 3. The VFR sectional chart depicting the airport identifier for Tradewind as TDW with L 51 as the maximum runway length for the airport.

As noted previously, L51 was the designator for Heller Farm Airport, Winifred, Montana, which was located about 586 nautical miles on a heading 354° from the accident site. 

WRECKAGE AND IMPACT INFORMATION

The accident site was located at latitude 37.76° north, longitude 107.84° west at an elevation of 11,500 ft. The wreckage path was estimated to be about 1,050 ft long along an estimated northerly direction in up-sloping mountainous terrain. See figures 4 and 5 for photographs of the wreckage.

Figure 4. Aerial view taken the day after the accident by first responders showing a white-colored object, which was a portion of the aircraft fuselage, resting on the face of up-sloping terrain. The photo also shows the cloud height at the time first responders arrived on-scene. The view of the western ridgeline averaged about 12,000 ft msl.

Figure 5. A photograph of the main wreckage, which was destroyed by impact forces with no evidence of soot or fire. The airplane wings, horizontal and vertical stabilizers, engines, and propellers were located at accident site.

Wreckage Examination

The largest piece of recovered wreckage was the tail section, which had the horizontal and vertical stabilizers attached. There was no evidence of soot or fire on the pieces of wreckage. Both engines were separated from the airframe. The propellers from both engines were separated from their hubs and displayed chordwise gouging/scratching and S-shaped bending/twisting. Accident impact damage to the airframe, accessories, and both engines precluded functional operational testing of these components/systems. 

The instrument panel was destroyed by impact forces, and none of the instruments were attached. The electrical, lighting, and ignition switches were destroyed.

The altimeter face was separated from its case, and the altimeter altitude indicator needles were not intact. The altimeter setting window of the face was intact and indicated a setting of 30.40 inches of mercury. 

The attitude indicator unit was separated from the instrument panel and crushed. The attitude indicator display was internally separated and loose within the unit and did not yield an attitude. The gyro within the attitude indicator was removed, and it showed circumferential scoring on the gyro and the gyro's housing.

The horizontal situation indicator heading select bug and compass both displayed about a 360° heading.

An oxygen bottle, consistent with a pilot oxygen system, was recovered, and its airworthiness/servicing was unknown due to the impact damage. A handheld GPS was not found/recovered from the accident site. The Hobbs meter and tachometers were destroyed.

The airplane's two fuel selector valve assemblies were separated from the airframe. One valve had its fuel selector control separated due to impact forces and was positioned to "off." The second valve was positioned to "main." 

Examination of the flight control system revealed that the flight control cables were attached to the control horns/bell cranks. Separated sections of the flight control cables exhibited broom straw features. 

Examination of both engines revealed no preimpact anomalies that would have precluded normal operation. 

MEDICAL AND PATHOLOGICAL INFORMATION 

The NTSB's Chief Medical Officer reviewed the pilot's and pilot-rated passenger's FAA medical case reviews, toxicology results, autopsy reports, the investigator's reports, and the audio tapes of the ATC conversations in Flagstaff. The pilot/airplane owner's personal medical records were obtained and reviewed. 

Pilot/Airplane Owner

The pilot's last aviation medical examination was dated December 17, 2013. According to the records, he was 70 inches tall, weighed 165 pounds, and had reported no chronic medical conditions and no medications to the FAA. He had reported a number of previous surgical procedures and a disability related to a military gunshot wound but the aviation medical examiner noted "no residual." 

Rocky Mountain Forensic Services, PLLC, performed an autopsy of the pilot. The autopsy report noted the cause of death was "multiple injuries" and the manner of death was "accident." Examination of the body for natural disease was limited by the severity of the pilot's injuries; no organs were available for evaluation. 

The FAA's Bioaeronautical Research Laboratory performed toxicology testing on the only available specimen, which was muscle, from the pilot. The testing identified ethanol at 0.015 gm/dl as well as citalopram and its metabolite N-desmethylcitalopram. Federal Aviation Regulations, Section 91.17 (a), prohibits any person from acting or attempting to act as a crewmember of a civil aircraft while having 0.040 gm/dl or more ethanol in the blood. Detected ethanol may be to the result of ingestion or microbial activity in the body after death.

Citalopram is an antidepressant that carries a warning: "May impair mental and/or physical ability required for the performance of potentially hazardous tasks (e.g., driving, operating heavy machinery)." However, it has not been shown to degrade performance in psychological testing experiments using healthy volunteers.

According to records obtained from the pilot's Veteran's Administration Hospital, in January 2013, he was documented as having multiple chronic medical conditions including spinal stenosis, hypothyroidism, depressive disorder, posttraumatic stress disorder, panic disorder, gastroesophageal reflux disease, esophageal stricture, chronic neck pain, paraplegia, peptic ulcer disease, type 2 diabetes, and emphysema. In a single note from an outside physician, the pilot's paraplegia was documented as relating to a motor vehicle accident in 1996.

The Veterans Administration records show that, in January 2015, the pilot was hospitalized for being unable to swallow. Eventually, he had a gastrostomy tube placed for feeding. He was admitted for a rotator cuff repair in March, 2015, and remained in the hospital for rehabilitation until May 2015. During that time, the feeding tube was removed. His active medications as of July 2015 included albuterol, formoterol, citalopram, hydromorphone (4mg tab every 4 active hours), aspart insulin (short acting), glargine insulin (long acting), levothyroxine, lidocaine patch, prazosin, and zolpidem.

Albuterol and formoterol are beta-agonists available as inhaled medication for the short-term treatment of wheezing and the longer term prevention of wheezing, respectively. Hydromorphone is an opioid analgesic Schedule II controlled substance available by prescription that is commonly marketed with the name Dilaudid and carries a warning about central nervous system depression so severe it may cause respiratory failure.

The pilot was on two forms of injected insulin: aspart, which is short acting, and glargine, which is long acting. Their common names are Novolog and Lantus, respectively. Levothyroxine is a replacement thyroid hormone typically used to treat hypothyroidism; it is commonly marketed with the name Synthroid. Lidocaine is a local anesthetic available in patch format to treat localized pain. Prazosin is a blood pressure medication commonly marketed with the name Minipress. Zolpidem is a short-acting sleep aid commonly marketed with the name Ambien and carries a warning about sedation and changes in judgment or behavior.

Finally, in a visit from September 1, 2015, the pilot was described as having a T12 spinal cord injury, "in a wheelchair but able to transfer."

Pilot-Rated Passenger

The pilot-rated passsenger's last aviation medical exam was dated May 28, 2015. At that time, he was 67 inches tall and weighed 255 pounds. He had previously reported high blood pressure to the FAA and reported using atenolol and naproxen as medications. 

Rocky Mountain Forensic Services, PLLC, performed an autopsy Rocky Mountain Forensic Services, PLLC. The autopsy reported the cause of death was "multiple injuries" and the manner of death was "accident." Examination of the body for natural disease was limited by the severity of the pilot's injuries; no organs were available for evaluation. 

The FAA's Bioaeronautical Research Laboratory performed toxicology testing on the only available specimen from the pilot-rated passenger, which was muscle. The testing identified ethanol at 0.043 gm/dl, as well as atenolol, diphenhydramine, and D-methamphetamine.

Atenolol is a medication used to treat high blood pressure and prevent recurrent heart attacks. It is commonly marketed with the name Tenorman. Diphenhydramine is a sedating antihistamine used to treat allergy symptoms and as a sleep aid. It is available over the counter under the trade names Benadryl and Unisom. Diphenhydramine carries the following Federal Drug Administration warning: "may impair mental and/or physical ability required for the performance of potentially hazardous tasks (e.g., driving, operating heavy machinery). Compared to other antihistamines, diphenhydramine causes marked sedation; it is also classed as a CNS depressant and this is the rationale for its use as a sleep aid. Altered mood and impaired cognitive and psychomotor performance may also be observed. In fact, in a driving simulator study, a single dose of diphenhydramine impaired driving ability more than a blood alcohol concentration of 0.100%."

Methamphetamine is a Schedule II controlled substance and is available in low doses by prescription to treat attention deficit hyperactivity disorder, attention deficit disorder, obesity, and narcolepsy. It is also commonly available as a street drug. Even in prescription form, methamphetamine can cause a host of physiological and psychoactive effects.


NTSB Identification: CEN15FA400
14 CFR Part 91: General Aviation
Accident occurred Saturday, September 05, 2015 in Silverton, CO
Probable Cause Approval Date: 04/19/2017
Aircraft: CESSNA 310H, registration: N1099Q
Injuries: 4 Fatal.

NTSB investigators either traveled in support of this investigation or conducted a significant amount of investigative work without any travel, and used data obtained from various sources to prepare this aircraft accident report.

The airplane owner, who was a noninstrument-rated private pilot and did not hold a multiengine airplane rating, was conducting a visual flight rules (VFR), personal cross-county flight in the multiengine airplane. Before the accident flight, the pilot flew the airplane to an intermediate airport to refuel. A review of air traffic control (ATC) radio transmissions between the pilot and an air traffic controller between 0911 and 0938 showed that, during the approach for landing, the pilot misidentified in every transmission the make and model airplane he was flying, referring to his airplane as a Piper Comanche instead of a Cessna 310. Further, he did not provide correct responses to the controller's instructions (for example, he reported he was set up for the left base leg instead of right base leg as instructed), and he provided inaccurate information about the airplane's position, including its distance and direction from the airport. 

A witness stated that, after the airplane landed and while it was taxiing, it almost hit another airplane and golf carts, and it was taxied close enough to the fuel pumps that it "knocked" a ladder with one of its propellers. The witness said that the pilot was not "observant about his surroundings." While at the intermediate airport, the pilot requested an abbreviated weather briefing for a VFR flight from that airport to the destination airport. However, the pilot incorrectly identified the destination airport as "L51," which was depicted on the VFR sectional chart for the Amarillo area but referred to the maximum runway length available at the destination airport not the airport itself. L51 was an airport identifier assigned to an airport in another state and located north of the accident location and in a direction consistent with the airplane's direction of travel at the time of the acident. 

During the departure for the accident flight, the pilot taxied to and attempted to take off from an active runway without any radio communications with or clearance from ATC, which resulted in a runway incursion of an air carrier flight on final approach for landing to the runway. The air carrier initiated a missed approach and landed without further incident. The controller reported that the runway incursion was due to the accident pilot's loss of "situational awareness." Radar data showed that, after the airplane departed, it turned northward and away from a course to the intended destination airport. The northward turn and track was consistent with a course to an airport in another state. According to meteorological information, as the flight progressed northward, it likely encountered instrument meteorological conditions (IMC) while flying into rain showers. The wreckage was found in rising mountainous terrain, and the accident wreckage distribution was consistent with a low-angle, high-speed impact. Given that postaccident examination of the airplane revealed no mechanical anomalies that would have precluded normal operation, it is likely that the noninstrument-rated pilot did not see the rising mountainous terrain given the IMC and flew directly into it. 

The pilot had told person(s) that he flew F-4 Phantoms, but a military identification card showed that the pilot was a retired Marine lance corporal. Although the pilot's logbook showed that he had accumulated 150 hours of multiengine airplane flight time, there was no record of the actual flights showing the accumulation of 150 multiengine airplane hours or any record that he had flown military aircraft. The logbook did not show that the pilot had received any flight training in the accident airplane. The logbooks also showed that he had flown numerous flights in the airplane with passengers without proper certification and that he had not had a recent flight review as required by Federal Aviation Regulations (FARs). The pilot's logbook showed that he had once made low-altitude (10 ft above the ground) passes over a parade in the same airplane. The airplane had not received an annual inspection for continued airworthiness as required by FARs. The pilot's noncompliance with FARs and the logbook entries indicate that he had a history of poor decision-making and piloting errors, which was reflected in his behavior and actions while landing at the intermediate airport and during the taxi and takeoff phases of the accident flight. 

Although the pilot had a number of medical problems that potentially could have interfered with his ability to safely operate the airplane, including spinal cord injuries, diabetes, and psychiatric issues, and was taking medications to treat them, these conditions and medications likely would not have interfered with his navigational skills and his ability to communicate on the radio or affected his decision-making. Although the available medical information was limited by the degree of damage to the body, there was no evidence of a medical condition or effects of a medication that contributed to this accident. Although ethanol was detected in the pilot's tissues, it likely resulted from postmortem production.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The noninstrument-rated pilot's improper judgment and his failure to maintain situational awareness, which resulted in the flight's encounter with instrument meteorological conditions and controlled flight into terrain during cruise flight.


NTSB Identification: CEN15FA400
14 CFR Part 91: General Aviation
Accident occurred Saturday, September 05, 2015 in Silverton, CO
Aircraft: CESSNA 310H, registration: N1099Q
Injuries: 4 Fatal.

NTSB investigators either traveled in support of this investigation or conducted a significant amount of investigative work without any travel, and used data obtained from various sources to prepare this aircraft accident report.

HISTORY OF FLIGHT

On September 5, 2015, about 1408 mountain daylight time a Cessna 310H, N1099Q, impacted mountainous terrain near Silverton, Colorado. The private pilot, a pilot-rated passenger, and two passengers were fatally injured. The airplane was destroyed by impact forces. The airplane was registered to and operated by the pilot as a 14 Code of Federal Regulations Part 91 a personal flight. Instrument meteorological conditions (IMC) prevailed at the time of the accident, and no flight plan had been filed. The pilot was not using air traffic control (ATC) services. The flight departed from Flagstaff Pulliam Airport (FLG), Flagstaff, Arizona, about 1150 and was destined for Tradewind Airport (TDW), Amarillo, Texas.

A fuel receipt from the Big Bear City Airport (L35), Big Bear, California, showed that 20.04 gallons of fuel was purchased for the airplane on September 4, 2015.

The pilot's daughter stated that the airplane was kept at L35 during the summer and afterward at Barstow-Daggett Airport (DAG), Daggett, California. She said that her father departed from L35 on September 5, 2015, about 0615 PDT, and arrived at DAG about 0630 PDT to pick up the passengers. He was then going to fly to Amarillo, Texas, following Interstate 40, where they were going to have dinner and then return the same day. She said that her father did not call her after he refueled and departed Flagstaff and that she called for help on September 6 because she had not heard from him. She said that there was another pilot aboard and that they had a GPS. She said that her father did not know anyone in Colorado or Montana.

A part-time Unicom operator at L35 said that the pilot talked about conducting the flight about 1 week before the accident. The pilot asked "a lot of different pilots to go along as copilot" and asked him to go on the flight. The Unicom operator did not know what time the pilot departed on September 5, but "it was pretty early in the morning" when the pilot left to pick up passengers. The Unicom operator stated that the pilot purchased the airplane "not too long ago," that the airplane radios were "very old," and that the "instruments were not all that good." 

The pilot's initial contact with an air traffic control (ATC) facility on the day of the accident occurred during a visual approach to FLG. A rerecording of provided radio transmissions between the pilot and an FLG air traffic controller between 1011 and 1038 follows:

N1099Q: "Flagstaff traffic this is Piper Comanche N1099Z I'm sorry quebec we're approximately thirty miles miles west of the field anybody know what how the weather is down there you socked in there cause we are flying over the top here."

FLG tower: "Comanche 1099Q flagstaff tower we are open. The uh the ATIS is also broadcasting we're 900 broken, 1,600 broken, 2,400 overcast, visibility 10." 

N1099Q: "Oh thank you I just turned the ATIS then. I appreciate it thank you Flagstaff."

N1099Q: "Flagstaff tower 1099Q about to land we are we are approximately 10 miles west of the airport." 

FLG tower: "Comanche uh 99Q flagstaff tower the uh we're IFR at the airport 900 broken 1600 broken visibility 10."

1099Q: "We are now approximately 8,000 feet we have visibility looks like greater than 10 miles." 

FLG tower: "Comanche 99Q I concur with the visibility uh are you requesting something special."

FLG tower: "Comanche 99Q the field is now VFR the uh ceiling is well I have a scattered layer of 1,200 ceiling 1,600 report a right base for runway 21."

N1099Q: "Report right base for runway 21 will do quebec."

FLG tower: "Comanche 99Q uh verify you have information charlie."

N1099Q: "Copy that we have we got a little bit of a … here."

FLG tower: "Comanche 99Q roger the wind is 220 at 8 temperature 16 density altitude is 8,400 dew point 13 and the altimeter 30.26."

N1099Q: "30.36 thank you."

FLG tower: "altimeter 30.26 26."

N1099Q: "Flagstaff tower this is quebec were gonna report left base runway 21 I just want to confirm that quebec."

FLG tower: "Comanche 99Q are you set up for a right base or a left base you're coming from the west you said."

N1099Q: "Oh its showing left base on my uh GPS left traffic on runway 21."

FLG tower: "Comanche 99Q uh we can make whichever way you want I just need to know which direction you're coming from."

N1099: "Well we're comin we're we're coming from 270 right now." 

FLG tower: "From 270 you should be west of the…airport where was the destination you left from."

N1099Q: "Well we can report let's see the winds are from uh what."

FLG tower: "Comanche 99Q the wind is 240 at 6 just report base."

N1099Q: "Well… we're…right now…"

FLG tower: "Comanche 99Q that came in broken and unreliable."

N1099Q: "The winds are 210."

FLG tower: "Wind 210 at 8."

FLG tower: "Comanche 99Q how far from the airport are you."

N1099Q: "We're downwind 21 left we're settin up for uh base for 21 left."

FLG tower: "Okay we only have runway 21 okay I see you now you are on a left downwind runway 21 cleared to land wind 210 at 8."

FLG tower: "Comanche 99Q runway 21 cleared to land."

N1099Q: "…the end of the runway now…on the downwind we'll make base to final."

FLG tower: "Comanche 99Q runway 21 cleared to land."

N1099Q: "Cleared to land runway 21."

FLG tower: "N99Q are you going to uh wiseman aviation the FBO."

N1099Q: "Yes we want to gas up can we exit."

FLG tower: "N99Q continue on the runway turn right alpha seven self-serve fuel will be towards the base of the rotating beacon if you want the uh FBO it's a green building near the uh rotating beacon."

N1099Q: "Okay I see the rotating beacon I guess we can make a right taxi here."

FLG tower: "N99Q you make right turn alpha seven that will get you more direct."

N1099Q: "Gotcha alpha seven."

N1099Q: "Flagstaff…down and clear of runway taxi to fuel pump."

N1099Q: "Yep."

N1099Q: "Quebec gettin ready to touchdown here runway 21 here flagstaff."

A fixed-base operator (FBO) employee at FLG stated that, during the airplane's taxi to the fuel pumps, the airplane almost hit an "Eclipse jet," and he thought it was going to hit golf carts that were near the FBO building. When the airplane arrived, it taxied close enough to the self-serve fuel pumps that it "knocked" a ladder with one of its propellers. He said that the pilot was not "observant about his surroundings." The airplane had white "house letters" painted on its side similar to those on fighter or Air Force aircraft. The house letters had "pilot" followed by a name, which he could not remember seeing, and "copilot" followed by "God." The airplane "looked clean.". The employee stated that the pilot told him that he hoped there were no more clouds, there was no more weather, and that he wanted 75 gallons of fuel for the airplane. The pilot pointed east and added that it should be 2 more hours to their destination. The employee thought the destination was Amarillo but was certain that it was in Texas.

The FBO employee said he showed the pilot how to use the fuel pump. The pilot gave the fuel order and payed for the fuel with cash. A passenger helped fuel the airplane at the self-serve fuel pump; he added about 15 gallons of fuel to the left and right wing fuel tanks (auxiliary fuel tanks) and put the fuel caps back on. The wing tip fuel tanks (main fuel tanks) were topped off. 

The FBO employee stated that another passenger said that he bought a "brand new GPS" and could not get "ADAS[Automated Weather Observing System Data Acquisition System]" to work and thought he also said, "oh well we'll figure it out later."

At 1054, the pilot called Lockheed Martin Flight Services (LMFS) while at FLG and requested an abbreviated weather briefing for a visual flight rules flight from FLG to Amarillo, Texas. The pilot told the weather briefer that the Amarillo, Texas, airport identifier was "L51"; this was not the correct identifier for Tradewind Airport. The correct identifier was TDW; the L51 airport identifier was assigned to Heller Farm Airport, Winifred, Montana. Despite providing the weather briefer with the wrong airport identifier, the briefer did provide information for the flight to Amarillo. The pilot received the latest weather information in the briefing, which included Airmen's Meteorological Information for mountain obscuration, convective outlooks (the briefer mentioned that there was no convective activity yet but told the pilot to stay updated via Flight Watch), the terminal aerodrome forecast for Rick Husband Amarillo International Airport, Amarillo, Texas, the Meteorological Terminal Aviation Routine Weather Report for Tucumcari Municipal Airport, Tucumcari, New Mexico, and the winds aloft at 9,000 and 12,000 ft between the departure and destination airports. No record was found indicating that the accident pilot received or retrieved any other weather information before or during the flight.

The FBO employee at FLG stated that, after the airplane was fueled, it taxied past the FLG ATC tower without making any radio communications with ATC. The airplane taxied onto a runway while an "air shuttle" was landing, and the air shuttle (SkyWest 2992) had to abort its landing. The pilot then turned the radio on and taxied off the runway and onto a taxiway near the air carrier ramp. A FLG airport rescue and firefighting (ARFF) employee drove to the airplane to talk to the pilot. The ARFF personnel told the left front pilot seat occupant that he had to move the airplane because it was blocking an air carrier ramp entrance. The employee said that FLG ATC had a "lengthy conversation" with the pilot after he had taxied the airplane off the runway and was told to call the FLG ATC tower. The employee said that he overheard on the FLG ATC frequency the air shuttle pilot asking about the airplane, and FLG ATC responded by saying it was "a case of situational awareness."

According to an Air Traffic Mandatory Occurrence Report, SkyWest 2992, CRJ2/L, was on the instrument landing system (ILS) runway 21 approach and was cleared to land on runway 21. The accident airplane was observed northbound on taxiway A without authorization from the FLG tower. N1099Q turned right onto the connecting taxiway A2 continuing toward runway 21. At that time, the tower controller issued go-around instructions to SkyWest 2992 on about 1 1/2 mile final and coordinated missed approach instructions with Phoenix Approach. The accident airplane continued onto runway 21 and initiated the takeoff roll and then established communication with the tower. The tower controller instructed the accident pilot to cancel takeoff and exit the runway. SkyWest 2992 was vectored back to the ILS approach course and landed without further incident.

The FLG ATC tower controller stated that, during his telephone conversation with the accident pilot following the runway incursion, the pilot "kind of missed the point," "came up with excuses" for the runway incursion, and did not know there was another airplane "out there" during the runway incursion. The controller stated that, when he told the pilot that there was an airliner on final, and it was at that point that the pilot "realized the gravity of the situation." The pilot then said that he had been flying for 50 years and nothing like this happened before. The controller said it "seemed" that the pilot "really didn't register" what had happened. The controller added that he did not remember having to repeat questions that he asked the pilot. The pilot did not seem upset nor did the pilot ask questions in response to the questions asked by the controller. The controller said that, during the second takeoff attempt, the accident airplane settled onto the runway after it had lifted off and then climbed out with a left turn.

The ARFF employee stated that the accident airplane taxied from the FBO to taxiway A2, held at A2, and then taxied onto an active runway with a commercial regional airplane on short final without any radio contact to ATC. The employee said that the accident pilot transmitted that he did not have the airplane's radio turned on or "something to that effect" and stated that they were going to take off. The employee said that the radio transmissions from the accident pilot were "screwy" and "lacked organization and context, and was not current."The employee said that it seemed like the pilot had spent a lot of time around uncontrolled airports. The employee said that during the airplane's second takeoff attempt, the airplane remained low over runway 21 for a long time and that, about 1,000 ft from the departure end of the runway, the airplane pulled up, "not steep," and entered a left turn to the east and headed northeast.

The flight was not receiving ATC services and was not assigned a transponder squawk code. The airplane used a squawk code of 1200 based upon ATC recordings and the arrival/departure times to and from FLG. The radar track of an airplane with a squawk code correlating to those times was plotted to provide an overview of the flight and is shown in figure 1.



Figure 1. A radar plot of an airplane flight track consistent with the accident airplane. The plot shows a turn toward the north. 

PERSONNEL INFORMATION

Pilot/Airplane Owner Information

The pilot, age 71, held a private pilot certificate with a single-engine land airplane rating. The pilot's most recent FAA third-class airman medical certificate was issued December 17, 2013, with the limitation that he must wear corrective lenses for near and distant vision. At that time, the pilot reported a total flight time of 1,000 hours, 200 hours of which were in last 6 months. There was no military record received showing that the pilot had any flight experience in military airplanes.



The pilot's daughter stated that her father flew F-4 Phantoms. An L35 employee reported that he believed that the pilot said he flew F-4 Phantoms in the military and transitioned to helicopters and was injured in Vietnam. A Department of Defense (DOD)/Uniformed Services identification card that belonged to the pilot was recovered from the accident site. The card showed that he served in the US Marine Corps at grade "E3," which according to DOD's Enlisted Rank Insignias was a grade of Lance Corporal.

The L35 employee said the pilot told him the he was a doctor and "had an MD." He stated that he researched the things told to him by the pilot, and none of it was true. He said the pilot had "some speech issues" and that he had a "high pitched garbled voice." He said that pilot could not "keep a fluent conversation" without having an "issue with talking." He said that the pilot's aircraft radio transmissions were "very short," which "concerned" him and L35 staff. He said "there were a lot of circumstances that concerned people about his [the pilot's] flying."

A review of the pilot's FAA airman record revealed that, on July 18, 2009, the pilot failed the practical portion of the examination in his first attempt for a private pilot certificate with a single-engine land airplane rating. Upon reexamination for the certificate/rating, he was to be reexamined on the following: IX. Basic Instrument Maneuvers, V. Performance Maneuver, and VII. Navigation. At the time of the examination, the pilot reported a total time of 301 hours and a total instruction time received of 52 hours. On September 21, 2009, the pilot successfully passed his second attempt and was issued a private pilot certificate with a single-engine land rating. At the time of reexamination, the pilot reported a total time of 305 hours and a total instruction time received of 55 hours. No record was found indicating that the pilot had been issued a multiengine airplane rating or that he had flown military aircraft..

The pilot's logbook, which was recovered from the accident site by first responders, had flight entries beginning July 7, 2007, and ending August 15, 2015. The logbook showed that the pilot's total flight time in single and multiengine airplanes was 801.9 hours, 255.6 hours of which were in single-engine airplanes and 217.7 hours of which were in multiengine airplanes. The first logbook page entry of a multiengine airplane flight time was dated January 6, 2013, in a Piper PA-23-250, N54155 and it showed a total multiengine flight time of 10.5 hours. The page also showed that the pilot's a total multiengine flight time for previous flights was 150 hours; however, there were no logbook entries documenting flights in multiengine airplanes before the page indicating that he had 150 hours of multiengine flight time. The pilot's logbook showed a total flight time in night conditions of 17.0 hours, of 0.2 hour of which was in the accident airplane. The most recent flight entry in night conditions was dated December 2, 2014, in the accident airplane for 0.1 hour. 

The accident airplane's Application for Registration to the pilot was dated June 27, 2014. The Aircraft Bill of Sale shows the airplane title was transferred to the pilot on July 2, 2014, from Aerobanc of America, Inc. The first flight entry in the pilot's logbook for the airplane was dated July 3, 2014. No record was found indicating that the pilot had received training in the airplane after its purchase/registration. The pilot's logbook contained a total of 72 flight entries for the airplane with a total flight time of 35.4 hours. During this period, the logbook's remarks sections had entries that showed the pilot had flown with passengers. There was one logbook entry dated March 7, 2015, for a flight in the airplane that had the following remark: "I let [name of pilot-rated passenger] fly part way back."

A logbook entry showed that the pilot's most recent flight review, as required by Part 61.56, was dated July 17, 2013, with a departure and destination of Apple Valley Airport, Apple Valley, California. The flight was in a Piper PA-28-180 with a flight time of 1.0 hour, a ground instruction time of 1.0 hour, and the remarks, "FAR 61.56 FLT. REVIEW VFR PROCEDURES." The flight review was conducted by the same flight instructor that had provided the pilot-rated passenger's flight review. Title 14 CFR Section 61.56(c) stated that a flight review must have been accomplished within the 24 calendar months preceding the month in which a pilot acts as pilot-in-command in an aircraft for which that pilot is rated. The pilot was overdue for his flight review by about 2 months.

A logbook entry dated July 4, 2012, showed a flight from DAG to DAG in a Piper PA-28-180 that was 1.0 hours in duration. The remarks section for the flight had the following entry: "Flew over parade 10 feet off ground made six passes." A logbook entry dated July 4, 2013, showed a flight from DAG to DAG in a Piper PA-28-180 that was 2.0 hour long. The remarks section for the flight had the following entry: "Landed on Rt. 66 4 July Parade. With Mayor." A logbook entry dated November 2, 2013, showed a flight from DAG to "Rt.66," in a Piper PA-28-180 that was 0.2 hour long. The remarks section for the flight had the following entry: "Flew to the barn landed on RT. 66 for auto show." According to 14 CFR 91.119, "Minimum safe altitudes," a pilot should not operate an aircraft at an altitude of 500 feet above the surface, except over open water or sparsely populated areas. In those cases, the aircraft may not be operated closer than 500 feet to any person, vessel, vehicle, or structure. 

A logbook entry dated June 14, 2014, showed a flight in a Piper PA-28-180 that was 2.0-hour long and included five landings from "DAG" to "Big Bear" with the remarks: "Young Eagles." Regarding this entry, the L35 employee reported that nothing at the time made him question the pilot's flying ability. He said the pilot wanted to fly in the Young Eagles program and that they have a large Young Eagles program at L35. He said that they had asked the pilot to produce the required paperwork for the Young Eagles program, but the pilot never produced the paperwork, so the program representative decided about 8 to 10 months before the accident to not allow the pilot to fly in the Young Eagles program.

A logbook entry dated August 15, 2015, showed a 0.3-hour-long flight in the accident airplane "L35" to "L35." The remarks section for the flight stated: "Big Bear airshow. made it. speed passes over runway." Regarding this entry, the L35 employee stated that there was "some issue" with the pilot during the Big Bear Airport air show. When the airport opened for departures, the pilot departed with passengers. Upon the pilot's return to the airport, he turned the airplane onto the final leg of the airport traffic pattern and did not have the airplane radio on. The shows's air boss cleared another airplane to depart from the active runway while the accident pilot was flying his airplane on short final. He stated that, instead of the pilot offsetting the airplane to the side of the runway during the go-around, the pilot performed a "low-level left turn over the crowd" with the landing gear and flaps extended. 

The pilot had no previous FAA record of accident(s), incidents(s), or enforcement(s) actions.A search of publically available information of airman certificate information from on the FAA's website, FAA.govGOV, using only the pilot/airplane owner's first and last name, revealed that the pilot/airplane owner only held a private pilot certificate with a single-engine land rating.

Pilot-Rated Passenger Information

The pilot-rated passenger, age 67, held a private pilot certificate with a single-engine land airplane rating. His most recent FAA third-class airman medical certificate was issued May 28, 2015, with the limitation that he must wear corrective lenses. At that time, he reported 1,000 hours of flight experience.

On March 25, 2003, the pilot-rated passenger successfully passed, on his first attempt, an examination for a private pilot certificate with a single-engine land airplane rating. At the time of examination the pilot-rated passenger reported a total time of 168 hours, and a total instruction time received of 90 hours.

The pilot-rated passenger's logbook, which was recovered from the accident site by first responders, had flight entries beginning February 26, 2009, and ending August 31, 2015. The logbook showed that his total flight time in all aircraft was 785.5 hours, all of which was in single-engine airplanes.

A logbook entry showed that the pilot-rated passenger's most recent flight review as required by Part 61.56 was dated June 11, 2015. The flight review was conducted by the same flight instructor who had provided the pilot's flight review.

The pilot-rated passenger's logbook showed a total flight time in night conditions of 17.0 hours. The most recent flight entry in night conditions was dated January 5, 2011. 

The pilot-rated passenger had no previous FAA record of accident(s), incident(s), or enforcement action(s).

AIRCRAFT INFORMATION

The accident airplane was a 1963 twin-engine Cessna 310H, serial number 310H-0099, airplane. It was powered by a Continental IO-470-VOCD, serial number 455693, engine and a Continental IO-470-D, serial number 79334, engine. The airplane was equipped with two 51-gallon capacity main fuel tanks and two 15.5-gallon capacity auxiliary fuel tanks. 

According to FAA airworthiness records, the most recent airworthiness certificate for the airplane was a Special Airworthiness Certificate dated April 11, 2006. The Special Airworthiness Certificate was a Special Flight Permit for the purpose of "Out of Annual Inspection – Maintenance." The airplane did not have a current airworthiness certificate at the time of the accident. A standard airworthiness certificate remains valid as long as the aircraft meets its approved type design, is in a condition for safe operation and maintenance, and preventative maintenance and alterations are performed in accordance with Parts 21, 43, and 91.

The pilot's daughter provided copies of the aircraft logbooks . These copies showed that the airplane's last annual inspection was dated May 1, 2014, at a Hobbs time of 1,541.3 hours and a total time in service of 5,367.3 hours.

Logbook entries annotated the left engine as serial number 455693 and the right engine as serial number 79334 and noted that the most recent annual inspections of the left and right engines were dated May 1, 2014. At the time of the inspections, the left engine had a time since major overhaul of 1,241.6 hours; the Hobbs time was not annotated. The right engine had a time since major overhaul of 858.4 hours and a Hobbs time of 1,541.3 hours.

Title 14 CFR 43.7 states that every airplane is required to undergo an annual inspection: "no person may operate an aircraft unless, within the preceding 12 calendar months, it has had an annual inspection and has been approved for return to service by a person authorized by Part 43.7."

METEOROLOGICAL INFORMATION

Astronomical Data

The astronomical data obtained from the United States Naval Observatory for the accident site on the day of the accident indicated that civil twilight began 0618, sunrise was 0645, sun transit was 1310, sunset was 1935, and civil twilight ended 2001.

Weather Information

Telluride Regional Airport (TEX), located 12 miles north-northwest of the accident site at an elevation of 9,070 ft mean sea level (msl) was the closest official weather station to the accident site. TEX had an Automated Weather Observing System, and its reports were not supplemented. 

At 1415, TEX reported wind from 190 degrees at 5 knots, 10 miles visibility, present weather thunderstorms in the vicinity, sky condition scattered clouds at 4,700 ft above ground level (agl), broken ceiling at 6,000 ft agl, broken skies at 7,000 ft agl, temperature of 17° C, dew point temperature of 7° C, and an altimeter setting of 30.34 inches of mercury. Remarks: automated station with a precipitation discriminator, lightning distant northwest, temperature 17.4° C, dew point temperature 6.6° C.

Closer to the accident site, observations from the nonofficial surface stations within 12 miles of the accident site reported gusting wind between 8 and 39 mph. The strongest wind was at the nonofficial surface stations closest to the accident site altitude and near the tops of the mountains between 10,000 and 12,000 ft. In addition, these stations reported rain showers in the vicinity and had relative humidity values greater than 80 percent around the accident time. These stations were above 10,000 ft, and the high relative humidity values were consistent with cloud cover at or above 10,000 ft and mountain obscuration due to clouds, precipitation, and mist. Figure 2 shows the three-dimensional Grand Junction, Colorado, weather surveillance radar-88 Doppler base reflectivity from the scan initiated at 1406 and the ATC Flight Track. 



Figure 2. Three-dimensional Grand Junction, Colorado, weather surveillance radar-88 Doppler base reflectivity from the scan initiated at 1406 and the ATC Flight Track. Blue and green colored areas depict reflectivity of greater than 10 decibels (dBZ) and greater than 20 dBZ, respectively.

AIRPORT INFORMATION

TDW was located about 482.7 nautical miles on a true course of 087° from FLG. The VFR sectional chart for the Amarillo area, shown in figure 3, depicted an airport identifier of TDW, not L51 as stated by the pilot, next to the airport name. L51 is shown once, but it referred to the maximum runway length available at TDW, which was 5,100 ft.





Figure 3. The VFR sectional chart depicting the airport identifier for Tradewind as TDW with L 51 as the maximum runway length for the airport.

As noted previously, L51 was the designator for Heller Farm Airport, Winifred, Montana, which was located about 586 nautical miles on a heading 354° from the accident site. 

WRECKAGE AND IMPACT INFORMATION

The accident site was located at latitude 37.76° north, longitude 107.84° west at an elevation of 11,500 ft. The wreckage path was estimated to be about 1,050 ft long along an estimated northerly direction in up-sloping mountainous terrain. See figures 4 and 5 for photographs of the wreckage.



Figure 4. Aerial view taken the day after the accident by first responders showing a white-colored object, which was a portion of the aircraft fuselage, resting on the face of up-sloping terrain. The photo also shows the cloud height at the time first responders arrived on-scene. The view of the western ridgeline averaged about 12,000 ft msl.





Figure 5. A photograph of the main wreckage, which was destroyed by impact forces with no evidence of soot or fire. The airplane wings, horizontal and vertical stabilizers, engines, and propellers were located at accident site.

Wreckage Examination

The largest piece of recovered wreckage was the tail section, which had the horizontal and vertical stabilizers attached. There was no evidence of soot or fire on the pieces of wreckage. Both engines were separated from the airframe. The propellers from both engines were separated from their hubs and displayed chordwise gouging/scratching and S-shaped bending/twisting. Accident impact damage to the airframe, accessories, and both engines precluded functional operational testing of these components/systems. 

The instrument panel was destroyed by impact forces, and none of the instruments were attached. The electrical, lighting, and ignition switches were destroyed.

The altimeter face was separated from its case, and the altimeter altitude indicator needles were not intact. The altimeter setting window of the face was intact and indicated a setting of 30.40 inches of mercury. 

The attitude indicator unit was separated from the instrument panel and crushed. The attitude indicator display was internally separated and loose within the unit and did not yield an attitude. The gyro within the attitude indicator was removed, and it showed circumferential scoring on the gyro and the gyro's housing.

The horizontal situation indicator heading select bug and compass both displayed about a 360° heading.

An oxygen bottle, consistent with a pilot oxygen system, was recovered, and its airworthiness/servicing was unknown due to the impact damage. A handheld GPS was not found/recovered from the accident site. The Hobbs meter and tachometers were destroyed.

The airplane's two fuel selector valve assemblies were separated from the airframe. One valve had its fuel selector control separated due to impact forces and was positioned to "off." The second valve was positioned to "main." 

Examination of the flight control system revealed that the flight control cables were attached to the control horns/bell cranks. Separated sections of the flight control cables exhibited broom straw features. 

Examination of both engines revealed no preimpact anomalies that would have precluded normal operation. 

MEDICAL AND PATHOLOGICAL INFORMATION 

The NTSB's Chief Medical Officer reviewed the pilot's and pilot-rated passenger's FAA medical case reviews, toxicology results, autopsy reports, the investigator's reports, and the audio tapes of the ATC conversations in Flagstaff. The pilot/airplane owner's personal medical records were obtained and reviewed. 

Pilot/Airplane Owner

The pilot's last aviation medical examination was dated December 17, 2013. According to the records, he was 70 inches tall, weighed 165 pounds, and had reported no chronic medical conditions and no medications to the FAA. He had reported a number of previous surgical procedures and a disability related to a military gunshot wound but the aviation medical examiner noted "no residual." 

Rocky Mountain Forensic Services, PLLC, performed an autopsy of the pilot. The autopsy report noted the cause of death was "multiple injuries" and the manner of death was "accident." Examination of the body for natural disease was limited by the severity of the pilot's injuries; no organs were available for evaluation. 

The FAA's Bioaeronautical Research Laboratory performed toxicology testing on the only available specimen, which was muscle, from the pilot. The testing identified ethanol at 0.015 gm/dl as well as citalopram and its metabolite N-desmethylcitalopram. Federal Aviation Regulations, Section 91.17 (a), prohibits any person from acting or attempting to act as a crewmember of a civil aircraft while having 0.040 gm/dl or more ethanol in the blood. Detected ethanol may be to the result of ingestion or microbial activity in the body after death.

Citalopram is an antidepressant that carries a warning: "May impair mental and/or physical ability required for the performance of potentially hazardous tasks (e.g., driving, operating heavy machinery)." However, it has not been shown to degrade performance in psychological testing experiments using healthy volunteers.

According to records obtained from the pilot's Veteran's Administration Hospital, in January 2013, he was documented as having multiple chronic medical conditions including spinal stenosis, hypothyroidism, depressive disorder, posttraumatic stress disorder, panic disorder, gastroesophageal reflux disease, esophageal stricture, chronic neck pain, paraplegia, peptic ulcer disease, type 2 diabetes, and emphysema. In a single note from an outside physician, the pilot's paraplegia was documented as relating to a motor vehicle accident in 1996.

The Veterans Administration records show that, in January 2015, the pilot was hospitalized for being unable to swallow. Eventually, he had a gastrostomy tube placed for feeding. He was admitted for a rotator cuff repair in March, 2015, and remained in the hospital for rehabilitation until May 2015. During that time, the feeding tube was removed. His active medications as of July 2015 included albuterol, formoterol, citalopram, hydromorphone (4mg tab every 4 active hours), aspart insulin (short acting), glargine insulin (long acting), levothyroxine, lidocaine patch, prazosin, and zolpidem.

Albuterol and formoterol are beta-agonists available as inhaled medication for the short-term treatment of wheezing and the longer term prevention of wheezing, respectively. Hydromorphone is an opioid analgesic Schedule II controlled substance available by prescription that is commonly marketed with the name Dilaudid and carries a warning about central nervous system depression so severe it may cause respiratory failure.

The pilot was on two forms of injected insulin: aspart, which is short acting, and glargine, which is long acting. Their common names are Novolog and Lantus, respectively. Levothyroxine is a replacement thyroid hormone typically used to treat hypothyroidism; it is commonly marketed with the name Synthroid. Lidocaine is a local anesthetic available in patch format to treat localized pain. Prazosin is a blood pressure medication commonly marketed with the name Minipress. Zolpidem is a short-acting sleep aid commonly marketed with the name Ambien and carries a warning about sedation and changes in judgment or behavior.

Finally, in a visit from September 1, 2015, the pilot was described as having a T12 spinal cord injury, "in a wheelchair but able to transfer."

Pilot-Rated Passenger

The pilot-rated passsenger's last aviation medical exam was dated May 28, 2015. At that time, he was 67 inches tall and weighed 255 pounds. He had previously reported high blood pressure to the FAA and reported using atenolol and naproxen as medications. 

Rocky Mountain Forensic Services, PLLC, performed an autopsy Rocky Mountain Forensic Services, PLLC. The autopsy reported the cause of death was "multiple injuries" and the manner of death was "accident." Examination of the body for natural disease was limited by the severity of the pilot's injuries; no organs were available for evaluation. 

The FAA's Bioaeronautical Research Laboratory performed toxicology testing on the only available specimen from the pilot-rated passenger, which was muscle. The testing identified ethanol at 0.043 gm/dl, as well as atenolol, diphenhydramine, and D-methamphetamine.

Atenolol is a medication used to treat high blood pressure and prevent recurrent heart attacks. It is commonly marketed with the name Tenorman. Diphenhydramine is a sedating antihistamine used to treat allergy symptoms and as a sleep aid. It is available over the counter under the trade names Benadryl and Unisom. Diphenhydramine carries the following Federal Drug Administration warning: "may impair mental and/or physical ability required for the performance of potentially hazardous tasks (e.g., driving, operating heavy machinery). Compared to other antihistamines, diphenhydramine causes marked sedation; it is also classed as a CNS depressant and this is the rationale for its use as a sleep aid. Altered mood and impaired cognitive and psychomotor performance may also be observed. In fact, in a driving simulator study, a single dose of diphenhydramine impaired driving ability more than a blood alcohol concentration of 0.100%."

Methamphetamine is a Schedule II controlled substance and is available in low doses by prescription to treat attention deficit hyperactivity disorder, attention deficit disorder, obesity, and narcolepsy. It is also commonly available as a street drug. Even in prescription form, methamphetamine can cause a host of physiological and psychoactive effects.

NTSB Identification: CEN15FA400
14 CFR Part 91: General Aviation
Accident occurred Saturday, September 05, 2015 in Silverton, CO
Aircraft: CESSNA 310H, registration: N1099Q
Injuries: 4 Fatal.

This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. NTSB investigators either traveled in support of this investigation or conducted a significant amount of investigative work without any travel, and used data obtained from various sources to prepare this aircraft accident report.


On September 5, 2015, about 1408 mountain daylight time, a Cessna 310H, N1099Q, impacted mountainous terrain at an elevation of about 11,500 feet mean sea level near Silverton, Colorado, based upon preliminary radar information consistent with the flight. Two non-instrument, single-engine land rated private pilots and two passengers were fatally injured. The airplane was destroyed by impact forces. The airplane was registered to and operated by the registered pilot under 14 Code of Federal Regulations Part 91 as a personal flight that was not operating on a flight plan and was not utilizing flight following services by air traffic control. Instrument meteorological conditions prevailed at the time of the accident. The flight last departed from Flagstaff Pulliam Airport, Flagstaff, Arizona. and was destined to Amarillo, Texas.




Members of the San Juan County and La Plata County search and rescue teams at the scene of the plane crash on Monday, Sept. 7. The Colorado Air National Guard helicopter that airlifted them to the remote location is in the background.


The plane that crashed in San Juan County on Saturday, Sept. 5, encountered “instrument meteorological conditions” over western Colorado, but neither of the two pilots aboard was qualified to fly in such bad weather.

That’s one of the conclusions in a preliminary report released Thursday, Sept. 17, by the National Traffic Safety Board, which is investigating the plane crash that killed four California residents.

The NTSB report indicates the crash occurred at about 2:08 p.m. on Sept. 5, when the twin-engine Cessna 310H “impacted mountainous terrain at an elevation of about 11,500 feet.”


Weather was partly cloudy in Silverton that day, but there were some rain squalls and a thunderstorm was reported in the area.

The wreckage was located the following day near the head of Cascade Creek at Grizzly Peak, about nine miles west of Silverton.
 The preliminary NTSB report also points out that the two pilots aboard were not rated to fly a twin-engine plane and were not operating on a flight plan.

Additionally, the pilot was not utilizing ”flight-following services by air traffic control,” the NTSB reported.

San Juan County Sheriff Bruce Conrad identified the victims as pilot Harold Joseph Raggio, 72, of Big Bear, Calif., Steven Dale Wilkinson, 59, of Newberry Springs, Calif., Rosalinda Leslie, 57, of Hesperia, Calif., and Michael Lyle Riley, 59, of Barstow, Calif.


The location where Harold Raggio keeps his Cessna 310H was vacant Tuesday morning. Raggio's Cessna 310H crashed Sunday in the San Juan Mountains in Colorado.



DAGGETT — Newberry resident Reany Raggio said she will forever remember the last time she flew with her father.

Harold Raggio took his daughter up in his Cessina 310H last month during an airshow at Big Bear Airport. On Sunday, Reany Raggio received a phone call from Colorado authorities that her father died in a crash in the San Juan Mountains near Telluride, Colorado.

Reany Raggio said Tuesday that three others died in the crash. Harold Raggio's son-in-law, Steve Wilkinson, a friend, Mike Riley, and Riley's girlfriend,  Rosalinda Leslie were the passengers in the plane.
"We knew something was wrong Saturday night," Reany Raggio said. "We did find out Sunday. The flight rescue notified us."

Raggio was piloting the Cessna 310 that took off from Barstow-Daggett Airport at about 7 a.m. Saturday, according to Alan Hamm, operator of Daggett Aviation. Harold Raggio, according to the Associated Press, was heading for Amarillo, Texas. Raggio took off from Big Bear and flew into Barstow-Daggett Airport to pick up his passengers. According to his flight plan, Harold Raggio also stopped in Flagstaff, Arizona to refuel.

Harold Raggio moved to Big Bear recently, but was well known in Newberry Springs.

"He lived for flying," Newberry resident Paula Deel said Tuesday. She said it was common for Harold Raggio to give friends and Newberry Springs residents rides in his plane. She recalls Raggio landing his Cessna 310 on Route 66 for the the community's Fourth of July celebration.

"He was a great guy," Paul Deel said. "Anybody that wanted to fly, he would take them up and show them a good time."

Paul Deel said he took his grandchildren flying.

Reany Raggio said that was not unusual for her father.

"He would take anybody up," she said. "Underprivileged kids too. He did a lot of that. The plane was his life to him. He loved to fly."

She said she grew up in air shows with her father, who just turned 71 last month. The retired Marine pilot leaves behind his wife, Rose, three children, 10 grandchildren and two great-grandchildren. He would have celebrated his 50th wedding anniversary in January. Tanya Raggio and Harold Dewayne Raggio are the other children.

Harold Raggio survived being shot down in a helicopter in Vietnam, his daughter said.

According to the San Juan County Sheriff's Department, a ground crew reached the site near Silverton, Colorado at an elevation of about 11,600 feet, Sunday night and confirmed a crash. The Civil Air Patrol had been searching for a Texas-bound small plane that went missing Sunday afternoon.

The National Transportation Safety Board is investigating.

Source: http://www.desertdispatch.com


The identities of four people who died in a plane crash Sunday north of Purgatory Resort were released Tuesday, two of which were pilots not rated to fly the type of aircraft they were operating.

Initial reports indicated five people died in the crash. The San Juan County Sheriff’s Office listed those who perished as pilot Harold Joseph Raggio of Newberry Springs, California; Steven Dale Wilkinson, also of Newberry Springs; Rosalinda Leslie of Hesperia, California; and Michael Lyle Riley of Barstow, California, who also happens to be a pilot.

The plane crashed around 2 p.m. Sunday, and was found at 11,500-feet in the upper limits of the Cascade Creek on the east side of the canyon, inaccessible from road or trails. A sheriff’s office post to Facebook said four rescuers were flown in by helicopter to look for signs of life. The next morning, additional emergency crews arrived on scene, knowing none of the passengers had survived.

“Through great effort, the rescuers were able to confirm the identities, and bring home the remains of all four victims,” the Facebook post says.

Peter Knudson, spokesman for the National Transportation Safety Board, said the two pilots on board were rated to fly single-engine aircraft – not the multi-engine plane they were flying, a Cessna 310H.

Multi-engine aircraft are more complex to operate, and can be more difficult to handle in cases of emergencies, Knudson said.

The plan is to bring down the remaining wreckage on Thursday to an accessible location for a federal investigator to detail. Knudson said the debris field reached 300 yards in length. A preliminary report will be available within two weeks, but a final report could take up to a year.

Officials confirmed the aircraft left Barstow on Sunday morning en route to San Antonio – not Amarillo as previously reported. The plane was last seen refueling in Flagstaff, Arizona.

Knudson said the pilots were not on a flight plan or communicating with flight traffic control. Instead, he said the pilots were navigating with reference to looking outside as opposed to following a path.

A variety of factors – including weather, proper training, and equipment failure – will be taken into account during the investigation.

In addition to the sheriff’s office, Civil Air Patrol, the Air National Guard and La Plata County Search and Rescue all took part in the emergency response. The NTSB and FAA are now handling the investigation.

In 2013, Raggio and Riley were included on the FAA’s Airmen Certification Database, a list of pilots who have “met or exceeded the high educational, licensing and medical standards,” set by the federal agency. It was not immediately known whether they had any training for multi-engine aircraft, and had not reached a “rated” status.

Source: http://www.durangoherald.com


Five people died in a Cessna 310H that was found crashed in mountainous terrain in remote San Juan County, the National Transportation Safety Board confirmed. 

The plane is thought to have gone down at about 4:15 p.m. Sunday, NTSB spokesman Peter Knudson said.

A Cessna 310H was reported overdue by a family member, the Federal Aviation Administration said. That plane was headed from Barstow, Calif., for Amarillo, Texas, via Tucumcari, N.M., and was last seen departing Flagstaff, Ariz.

Neither agency could confirm whether the missing Cessna 310H is the same one whose wreckage was found. The nearest town to the crash site is Telluride, San Miguel County.

"There are still a lot of unanswered questions," Knudson said. "Early on, there's a lot we don't know."

The N-Number for the craft missing from Barstow shows a Cessna 310H registered to a Harold Raggio of Newberry Springs, Calif. Daggett Aviation, a fixed-base operator for the Barstow-Daggett airport, said Raggio had a hangar there, as well as in Big Bear, Calif., about 54 miles southwest.

Raggio's Cessna took off from Big Bear on Saturday, landed at Daggett to pick up passengers and took off for Flagstaff, according to Dagett Aviation.

An NTSB investigator was on the way to the crash site Monday; Knudson said he would likely have to be choppered in to access the wreckage.

Attempts to reach the San Juan County coroner Monday have so far been unsuccessful. The San Juan County Sheriff's dispatch referred calls to the NTSB.

Previous story:

Five people died in a Cessna 310H that was found crashed in mountainous terrain in remote San Juan County, the National Transportation Safety Board confirmed.

The plane is thought to have gone down at about 4:15 p.m. Sunday, NTSB spokesman Peter Knudson said.

A Cessna 310 was reported overdue by a family member, the Federal Aviation Administration said. That plane was headed for Amarillo, Texas, via Tucumcari, N.M., and was last seen departing Flagstaff, Ariz.

Neither agency could confirm whether the missing 310 is the same one whose wreckage was found. The nearest town to the crash site is Telluride, San Miguel County.

"There are still a lot of unanswered questions," Knudson said. "Early on, there's a lot we don't know."

Knudson did not expect to have additional information before late Monday night or Tuesday morning.

An NTSB investigator was on the way to the crash site as of 11:30 a.m. Monday; Knudson said he would likely have to be choppered in to access the wreckage.

He could not immediately provide the Cessna's N-number.

The Durango Herald reports that the search is taking place in the Grizzly Peak area and that a Civil Air Patrol crew, since recalled, launched from the Grand Junction Regional Airport on Sunday, shortly after receiving word of the missing plane.

The La Plata County Sheriff's Office is assisting the San Juan County Sheriff's Office in the crash response, as well.

Original story:

Plane wreckage found near Telluride may be that of an overdue Cessna 310, that was en route from Flagstaff, Ariz. to Amarillo, Texas, via Tucumcari, N.M.

Federal Aviation Administration officials have not confirmed whether the wreckage is that of the missing plane, which a relative of one of the passengers had reported as overdue.

Search and rescue teams are on scene, the FAA said. Investigators from that agency and from the National Transportation Safety Board are also expected to arrive on scene Monday.

There was no immediate word of the fate of those who may have been on board the aircraft.


The Durango Herald reports that the search is taking place in the Grizzly Peak area and that a Civil Air Patrol crew, since recalled, launched from the Grand Junction Regional Airport on Sunday, shortly after receiving word of the missing plane.


The La Plata County Sheriff's Office is assisting the San Juan County Sheriff's Office in the crash response, as well.


Source:  http://www.montrosepress.com


KUSA - Up to five people were killed in a plane crash that happened Sunday in a remote part of San Juan County.

The plane, a Cessna 310H, lost radio contact south of Telluride near Grizzly Peak and crashed at around 4:15 p.m., the National Transportation Security Board says.

Lt. Col. Mike Daniels with the Civil Air Patrol couldn't confirm that it was the same plane reported overdue that was traveling from Barstow, California to Amarillo, Texas.

The identities of the people on board have not yet been released. The San Juan County Sheriff's Office says all of their rescuers are safely out of the field, and are bringing home the remains of the passengers

Investigators from the FAA and NTSB are headed to the area to conduct an investigation -- and 9NEWS aviation expert and former NTSB investigator Greg Feith says the remoteness of the location could make getting answers a challenge.

"They don't have the ability to law the wreckage out, to utilize the tools they may need, so [investigators] will document as much of the wreckage they can, looking for certain characteristics, and once they've done everything they can on scene, the aircraft will probably be recovered and taken to a salvage yard where they can re-examine things that may have been more interesting on the scene," Feith said.