[Peetwo]

FSD Episode 133

Via the FSD podcast:

Human Factors Ignored on the Maintenance Floor – Episode 133

September 21, 2022/in Episodes /

An accident involving a Hughes 269C helicopter demonstrates the lack of depth in accidents attributed to maintenance errors. Once again, there is no analysis on the human factors involved among maintenance personnel.

The NTSB probable cause for this air crash points to an improperly installed mounting bracket on the engine. The supporting details and aviation insights are lacking.

“My frustration is that they go no further than to say this is a maintenance issue,” John Goglia says. “No human factors are explored although that is as important in maintenance as it is in the cockpit.”

John, Greg and Todd find many questions unanswered. They discuss the value in going deeper than “maintenance screwed up.”

They explore the many questions not investigated that could lead to information that people can learn from. They talk about why even the most benign accidents can result in aviation safety benefits. This accident report is among many that are a disservice to the aviation community because it is superficial.

Also in this episode, Greg retracts a Episode 131 statement that 50% of NTSB probably causes are wrong. He does not have sufficient documentation to support the statement. However, he stands by his statement that he is confident that at least half of NTSB reports are incomplete.

Helpful links:

• NTSB Public Docket, NTSB Number WPR14LA340
  
• NTSB Final Report (PDF)
  
• USA Today article, “Unchecked carnage: NTSB probes are skimpy for small-aircraft crashes”
  June 14 2014
  
• RAND Report, “Safety in the Skies” (PDF)
  

MTF...P2 

[Peetwo]

Speaking of midair collisions - 

Via Youtube:

Via Foxnews:

Dallas airshow disaster caught on video as planes collide in mid-air

A Boeing B-17 Flying Fortress and a Bell P-63 Kingcobra collided and crashed to the ground

Two planes collided in midair at the Wings Ove Dallas Airshow at the Dallas Executive Airport on Saturday afternoon.

The accident took place during the Wings Over Dallas World War II Airshow at 1:25 p.m.

"A Boeing B-17 Flying Fortress and a Bell P-63 Kingcobra collided and crashed at the Wings Over Dallas Airshow at Dallas Executive Airport in Texas around 1:20 p.m. local time Saturday," the Federal Aviation Administration said. "At this time, it is unknown how many people were on both aircraft."

I wonder if the NTSB will be refusing to investigate this one??

Answer:

The FAA and the National Transportation Safety Board said that they will investigate the incident.

MTF...P2 

[Peetwo]

Metro (with 56 dogs) ace's Western Lakes Golf Club (par 4) 3rd hole -   

Good news story for a change...

Airplane carrying 56 rescue dogs crash-lands on golf course, Wisconsin officials say

An airplane carrying precious cargo crashed on a Wisconsin golf course, officials said. Deputies with the Waukesha County Sheriff’s Office responded to the scene shortly after 9 a.m. on Nov. 15, the office said in a news release. There were three people and 56 rescue dogs aboard the flight, which crash-landed and came to rest on the third hole of the Western Lakes Golf Course, according to the sheriff’s office. The plane took “significant damage.” As the plane descended, its wings were clipped off by trees and the fuselage scraped belly-first across the green, officials told WDJT. Over 300 gallons of jet fuel leaked from the wreckage and the state Department of Natural Resources was on the scene. Despite the dangerous landing, all people and puppies survived with some sustaining minor injuries, the sheriff’s office said.

Read more at: https://www.newsobserver.com/news/nation...rylink=cpy

Ref: https://westernlakes.com/

MTF...P2 

[Peetwo]

Follow on from last - AAI good news story...

Via the FSD:

Aviation Safety & Animals – Episode 145

December 14, 2022/in Episodes /

More than 53 dogs being transported from New Orleans to Milwaukee had a bumpy ride when their cargo flight crashed on a golf course. This is a good news story with just a few minor injuries. John and Todd take the opportunity to put the focus on aviation safety for animals.

Animals are transported by air for a variety of reasons. There are some regulations to ensure their safety. However, Greg and Todd advise that anyone considering air transport for an animal do careful research and purchase a suitable travel carrier.

This crash involved a Fairchild Metroliner. The crash sheared off the wings and dumped a lot of jet fuel. Fortunately, there was no fire. Quick action by first responders recovered all the dogs and even led to a few adoptions!

Related document: More on aviation safety & animals – Dog-related accident mentioned in show, Miami Air 2019 in Jacksonville, FL (PDF)

Episode bonus: Meet Todd’s rescue pup Gidget!

MTF...P2 

[Peetwo]

NTSB critical of aspects of Ethiopian Flight ET 302 final report -  

Via Reuters:

December 30, 20223:46 AM GMT+11Last Updated a day ago

U.S. safety experts dispute aspects of Ethiopia 737-MAX air crash findings
Reuters

NAIROBI, Dec 28 (Reuters) - U.S. air safety experts say Ethiopian inspectors investigating the cause of an Ethiopian Airlines' crash that killed nearly 160 people in 2019 did not pay enough attention to crew training and emergency procedures in their report.

The United States National Transportation Safety Board (NTSB), in dissenting comments included in the Ethiopian report, disagreed with at least two key findings of the investigation into the crash of a Boeing 737-MAX flight.

Fight 302 crashed shortly after take-off from Addis Ababa in March 2019, killing all 157 people on board.

Ethiopia's Aircraft Investigation Bureau released its long-delayed report last Friday. It blamed the accident on "uncommanded" inputs from Boeing's Manoeuvring Characteristics Augmentation System, known as MCAS.

The inputs, which were caused by faulty data from an underlying sensor, sent the plane's nose down repeatedly, leading to loss of control as the pilots tried to deal with several warnings in the cabin, the report said.

But in its comments, the NTSB said it found the faulty sensor may have been damaged by a bird strike soon after take-off, an assertion that was ignored by the Ethiopian investigators.

The Ethiopians did not find any evidence that the sensor was damaged in flight due to lack of any physical clues like a dead bird in the vicinity of the flight's path, their report said.

The NTSB, however, said the sensor was never recovered at the crash site in spite of a partial search by both sides a week after the accident.

Ethiopian Federal policemen stand at the scene of the Ethiopian Airlines Flight ET 302 plane crash, near the town of Bishoftu, southeast of Addis Ababa, Ethiopia March 11, 2019. REUTERS/Tiksa Negeri

Boeing has previously said the MCAS was a safety feature and the issues identified after the crash of flight 302, which followed one of a similar plane in Indonesia five months earlier, have been rectified.

The NTSB also accused their Ethiopian counterparts of focusing on the contributions of the design issues to the accident at the expense of the crew's own training and reaction to the emergency that arose.

"Discussion of crew resource management and performance were still not sufficiently developed in the draft final report," the NTSB said.

The pilots were supposed to manually reduce throttle after the erroneous feeds from the sensor interfered with the expected automatic sequence, it said.

In their report, the Ethiopian investigators found that the crew members were licensed and qualified for flight in accordance with the existing Ethiopian Civil Aviation Rules and Standards, but were startled by the unprecedented change of events and "confusing alerts", and blamed it all on the plane's design.

"Flight crew situational awareness and ability to perceive each and every thing to the detail was greatly affected with the ever changing flight scenario and unsettling warnings and flight deck effects," the report said.

The investigation bureau referred Reuters to NTSB's statement when asked for further comments.

The accident involving Flight 302 followed another incident five months earlier, when the same model crashed in Indonesia, killing 189 people.

The accidents exposed a problem with a system on the plane, and the model was grounded worldwide, costing Boeing some $20 billion and prompting court cases that exposed shortcomings with the certification process.

Operators have since resumed flying the 737-MAX after the plane's 20-month grounding. Ethiopia was among the last countries to return the 737 MAX to service.

MTF...P2 

[Peetwo]

NTSB v Ethiopian Flight ET 302 FR: Part II

Courtesy Hessel W. van der Maten, via Linkedin: 

---

Hessel W. van der Maten

Aside from everybody’s opinion on responsibility, liability and accountability for the accident, this communication from the NTSB provides some good insight into an important part of the investigative process: draft report review.

ICAO Annex 13 stipulates who may participate in the investigation. While the State of Occurrence (here: Ethiopia) is in charge of the investigation, many accredited representatives provide information that could find its way into the final report. A draft of the final report is normally sent to those involved to collect feedback on factual accuracy. To maximize transparency, the investigative authority sometimes publishes this feedback, with their commentary on why this was or was not incorporated into the final report. This way, the reader can determine the objectivity, veracity and thoroughness of the investigation.

The NTSB decided to publish their feedback and I have no doubt this decision was not taken lightly. Investigative authorities are not supposed to apportion blame and this release only aims to increase transparency so that we can improve our learning and attempt to prevent reoccurrence.

NTSB Releases Comments on Ethiopia’s Investigation of the Boeing 737 Max Accident

12/27/2022

---

WASHINGTON (December 27, 2022) — The National Transportation Safety Board published Tuesday the comments it provided to the Ethiopian government on their draft accident investigation report into the 2019 crash in Ethiopia of a Boeing 737 Max airplane.

The NTSB took the unusual step of publishing the comments on its website after Ethiopia’s Aircraft Accident Investigation Bureau (EAIB) failed to include the NTSB’s comments in its final report on its investigation into the March 10, 2019, crash of Ethiopian Airlines flight 302, a Boeing 737-800 MAX. The NTSB received the EAIB final accident report on December 27.

In accordance with the provisions of the International Civil Aviation Organization Annex 13, countries participating in the investigation are provided the opportunity to review the draft report and provide comments to the investigative authority. If the investigating authority disagrees with the comments or declines to integrate them into the accident report, participating countries are entitled to request that their comments be appended to the final report.

The EAIB provided the NTSB with its first draft of the report last year. The NTSB reviewed the report and provided comments on several aspects of the accident the NTSB believed were insufficiently addressed in the draft report. The comments primarily were focused on areas related to human factors.

After the EAIB reviewed the comments, it provided the NTSB with a revised draft report for its review. The NTSB determined the revised report failed to sufficiently address its comments. As provided by the ICAO Annex 13 process, the NTSB provided the EAIB with more expansive and detailed comments.

Instead of incorporating the most recent and expanded comments into their report, or appending them as had been requested, the EAIB included a hyperlink in their final report to an earlier and now outdated version of the NTSB’s comments.

The NTSB also noted that the final report included significant changes from the last draft the EAIB provided the NTSB. As a result, the NTSB is in the process of carefully reviewing the EAIB final report to determine if there are any other comments that may be necessary.

The NTSB’s comments are available online.

MTF...P2 

[Peetwo]

Nepal plane crash in Pokhara?? - 

Via the other Aunty...

FWIW here is where the discussion is at on the UP...

Ref: https://www.pprune.org/accidents-close-c...st11367370

MTF...P2 

[Peetwo]

Wings over Dallas Midair collision; Airboss audio and transcript released under FOI - 

Courtesy CBS DFW, via Youtube:

---

A comment from cornishcactus which IMO absolutely nails it...

cornishcactus
5 days ago (edited)

The Airboss allowed the aircraft to all fly at the same height, he also kept the bombers further out from the crowd at the 1000' line while letting the fighters on the closer line.

As the bombers were making larger turns in the circuit this put the fighters on the inside of the turns so they had to cross the bombers paths to get to that closer crowd line.

This also increased their speed as they had to overtake and worse bank sharper which lowered their visibility.

There's no reason they couldn't have flown two separate circuits with the fighters on the outside at all times as their higher speed would allow them to fly the larger circuit quicker to get the over the flighline timings correct and keep everything together. This also affords the fighters the best view possible of the bombers at all times in turns as they appear above in the canopy and aren't obstructed by the engine, wing or sometimes thicker portion of the canopy hoop frame.

Or you have them separated by half a circuit at all times regardless. . .

Maybe the 'Airboss' (ATC) radio phraseology is standard for warbird air displays in the US but IMO it is nothing more than confusing gobbledygook and as blancoliro, in his summary presentation, states this is the 'smoking gun' in this NTSB AAI..

Plus a couple of comments, which again IMHO absolutely NAILS IT!

leokimvideo
5 days ago (edited)

Totally shocking hearing the cowboy Airboss controlling the aircraft. Explains why this incident happened. Incredibly chilling to hear the confusion building up before the collision. Surely the pilots flying this mayhem had a feeling it was all getting out of control. Sure the show must go on, but look what happens when it's allowed to. Criss cross flying pattern also caused the double helicopter crash in Australia at Sea World.

---

Jim Immler
5 days ago

I am a pilot with what I believe are good radio and situational awareness skills.  After listening to that three times I can only hope that I would have exited that pattern asap.  Very chaotic situation.  Somehow all parties got sucked into a very unrealistic situation with the potential for multiple points of failure.  Very sad.  As pilots we always need to evaluate and refuse a sketchy situation before going up.  I hope this never happens again and becomes a catalyst for future training.  My sincerest condolences to all families affected by this.

   

MTF...P2 

[Peetwo]

Blan Colirio Nepal ATR 72 Crash summary - 

Ref:

Nepal plane crash in Pokhara?? - 

Via the other Aunty...

FWIW here is where the discussion is at on the UP...

Ref: https://www.pprune.org/accidents-close-c...st11367370

Via Youtube:

438,334 views  16 Jan 2023
LINKS:
ASN: https://aviation-safety.net/database/rec...20230115-0
Twitter: https://twitter.com/AirCrash_/status/161...n-nepal%2F
FR24: https://www.flightradar24.com/data/aircr...c#2edb480c

MTF...P2 

[Peetwo]

NTSB continues critique of EAIB Max 8 Final Report - 

Via AvWeb:

NTSB Announces Detailed Criticism Of Ethiopia’s Max 8 Accident Findings

By Mark Phelps -Published: January 24, 2023



Almost a month after releasing comments criticizing the Ethiopian Aircraft Accident Investigation Bureau (EAIB) for its final report on the March 2019 fatal accident of a Boeing 737 Max 8, the U.S. National Transportation Safety Board (NTSB) today (Jan. 24) released new comments challenging the Ethiopians. Today’s comments offer details involving the EAIB’s conclusion as to the source of faulty angle-of-attack data and “insufficient attention to the human performance aspects of the accident.”

While the board’s Dec. 27, 2022, statement acknowledged the role of the Max 8’s much-criticized Maneuvering Characteristics Augmentation System (MCAS) in the accident that killed all on board Ethiopian Airlines Flight 302 shortly after takeoff, the NTSB now says that the EAIB’s report unfairly blamed the manufacturer for electrical problems that caused erroneous angle-of-attack output.

Today’s NTSB statement read, in part, “The EAIB wrote electrical anomalies that existed since the time of the accident airplane’s production [italics added] caused the AOA sensor heater to fail, which resulted in the AOA sensor providing erroneous values that caused MCAS to repeatedly pitch the nose of the airplane downward until it struck the ground.

“But the NTSB found the erroneous AOA sensor output was caused by separation of the AOA sensor vane due to impact with a foreign object [italics added], which was most likely a bird. During the accident investigation, the NTSB provided the EAIB with evidence supporting this finding, but that evidence was not included in the final report.”

The board further wrote, “The AOA sensor vane heater’s function is to prevent ice formation that could restrict vane movement. The conditions present at the time of the accident were above freezing temperatures with no moisture present (that is, ice could not form regardless of the heater’s operational status). Thus, a loss of electrical current through the vane heater at any time during the accident flight would not explain the event because the loss of electrical current would have had no effect on the AOA sensor output.”

The NTSB also cited as “misleading” the EAIB’s findings on Boeing’s alleged lack of documentation for flight crews regarding the correct procedures in the event of a failed sensor causing the MCAS system to induce nose-down autopilot flight commands. “Boeing had provided the information to all 737 Max operators four months before the Ethiopian Airlines crash,” according to today’s NTSB statement.

MTF...P2 

[Peetwo]

NTSB release FR into LA Augusta chopper prang - 

Very graphic video footage, courtesy Aviation Accidents/This day in history, via Youtube:

On November 6, 2020, about 1500 Pacific daylight time, an Agusta (Leonardo) A109S helicopter, N109EX, was substantially damaged when it was involved in an accident at the University of Southern California, Keck Medical Center, Los Angeles, California. The pilot and one passenger sustained serious injuries, and one passenger were uninjured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 135 helicopter air ambulance flight.

The pilot established the helicopter in an approach to land on a rooftop helipad. During the approach, as the helicopter was about 40 ft above the helipad, the helicopter began to yaw to the right despite the pilot’s control inputs. As the pilot continued the approach, he experienced a loss of tail rotor control and attempted to land on the helipad as the helicopter’s right yaw increased. A witness videoed the accident sequence which showed the helicopter rotating clockwise about the vertical axis and rolling to the left before it impacted the helipad. Postaccident examination of the helicopter revealed that the ring nut for the tail rotor duplex bearing was backed out of the sleeve, which resulted in the loss of tail rotor control.

During the investigation, the manufacturer provided historical records of four previous cases that involved ring nut failures. These cases resulted in the manufacturer developing changes to maintenance practices, issuance of European Union Aviation Safety Agency Emergency Airworthiness Directive 2012-0195E in September 2012, and the issuance of Federal Aviation Administration Airworthiness Directive (AD) 2014-02-08, in March 2014, which was superseded by AD 2015-11-08, in June 2015, as a result of a fourth occurrence. The AD added, in part, a daily pilot check to enhance detection of an impending failure of a tail rotor duplex bearing ring nut installation.

The accident pilot and the previous pilot who was assigned to the helicopter reported visually inspecting the two locking wires and signing off on the inspection.

Probable Cause: The loss of tail rotor control due to the separation of the tail rotor duplex bearing ring nut from the thrust sleeve, which resulted in the loss of helicopter control.

Very lucky the chopper came to rest on the rooftop helipad, literally centimetres from falling off the edge of the building...coming to a vertiport near you??  

MTF...P2 

[Peetwo]

TAIC NZ request ATSB lab rat assistance with B777 runway excursion -   

Via Popinjay central:

Investigation number AE-2023-001
Occurrence date 27/01/2023
Location Auckland, New Zealand
State International
Report status Pending
Investigation type External Investigation
Investigation phase Evidence collection
Investigation status Active
Anticipated completion Q1 2023

Summary

On 27 January 2023 a Boeing 777 aircraft registered ZK-OKN, was conducting a scheduled passenger flight from Melbourne, Australia to Auckland, New Zealand. Shortly after touchdown at Auckland airport, the aircraft briefly lost directional control and the aircraft veered away from the runway centreline. There was damage reported to six runway edge lights and to the aircraft’s undercarriage assembly, including deflation of one tyre, there were no injuries to passengers or crew.

The Transport Accident Investigation Commission (TAIC) has requested assistance from the Australian Transport Safety Bureau (ATSB) to download the aircraft’s cockpit voice recorder (CVR) and flight data recorder (FDR) to assist their investigation.

To facilitate this support and to provide the appropriate protections for the information, the ATSB appointed an accredited representative in accordance with paragraph 5.23 of ICAO Annex 13 and commenced an investigation under the Australian Transport Safety Investigation Act 2003.

 
Hmm..27th of January...flooded runway perhaps??

MTF...P2

[Peetwo]

Austin Texas near miss LOSA occurrence - 

Via blancoliro:

For those of you on Twitter, you can view a simulated video sequence of the incident here: https://twitter.com/PAIN_NET1/status/162...6163220480 (remember the actual conditions were low visibility and ceiling)

Next the ATC audio and ADSB overlay view:

Finally via the MSM:

MTF...P2 

[Peetwo]

PC12 fatal inflight breakup - 

Via AvWeb:

PC-12 Medevac Broke Up, Five Killed (Updated)

By Russ Niles -Published: February 25, 2023 Updated: February 27, 2023



The NTSB says a Pilatus PC-12 medevac aircraft broke up in flight shortly after taking off from Reno Airport on Friday night. All five people aboard the Care Flight aircraft were killed when the aircraft suddenly disappeared from radar as it was climbing on departure from Reno International Airport to Salt Lake City Friday evening. The wreckage was found near Dayton, Nevada, about 24 miles southeast of Reno. The missing parts were about 1200 yards from the main wreckage.

Flight trackers showed the plane at about 19,000 feet before contact was lost. According to an ATC recording, a controller had just warned the pilot of generalized light to moderate turbulence in the area and the pilot said he was climbing to 25,000 feet. A winter storm was hitting the area at the time.

The NTSB sent a full investigation team of 11 members to the site and held a news conference on Sunday to discuss their initial findings. The investigators said part of the right wing, the horizontal stabilizer and elevator all separated from the plane. Although ATC had notified the pilot about the possibility of turbulence, the NTSB said there had been no reports that would have warranted cancelling the flight. “It was pretty much a normal evening,” NTSB Vice Chairman Bruce Landsberg told the news conference. The pilot, a nurse, a paramedic, the patient and a relative of the patient were on the aircraft.

RIP! - MTF...P2 

[Peetwo]

PC12 fatal inflight breakup - 

Via AvWeb:

PC-12 Medevac Broke Up, Five Killed (Updated)

By Russ Niles -Published: February 25, 2023 Updated: February 27, 2023



The NTSB says a Pilatus PC-12 medevac aircraft broke up in flight shortly after taking off from Reno Airport on Friday night. All five people aboard the Care Flight aircraft were killed when the aircraft suddenly disappeared from radar as it was climbing on departure from Reno International Airport to Salt Lake City Friday evening. The wreckage was found near Dayton, Nevada, about 24 miles southeast of Reno. The missing parts were about 1200 yards from the main wreckage.

Flight trackers showed the plane at about 19,000 feet before contact was lost. According to an ATC recording, a controller had just warned the pilot of generalized light to moderate turbulence in the area and the pilot said he was climbing to 25,000 feet. A winter storm was hitting the area at the time.

The NTSB sent a full investigation team of 11 members to the site and held a news conference on Sunday to discuss their initial findings. The investigators said part of the right wing, the horizontal stabilizer and elevator all separated from the plane. Although ATC had notified the pilot about the possibility of turbulence, the NTSB said there had been no reports that would have warranted cancelling the flight. “It was pretty much a normal evening,” NTSB Vice Chairman Bruce Landsberg told the news conference. The pilot, a nurse, a paramedic, the patient and a relative of the patient were on the aircraft.

RIP! - MTF...P2 

Addendum: 

[Peetwo]

FSD review Yeti Air Crash preliminary report - 

Courtesy FSD, via Youtube:

Yeti Air Crash Preliminary Report – Episode 157

The Flight Safety Detectives examine the preliminary accident report from the fatal January 2023 Yeti air crash. They discuss professionalism and crew resource management as the central cause.

“Pilots needs to execute with purpose,” Greg Feith says. “That means that before you do or touch anything in the cockpit you have to be clear about your purpose.”

Greg, Todd Curtis, and John Goglia share possible reasons why the Yeti Airlines ATR 72 flight crew made fundamental errors that allowed the aircraft to stall and crash shortly before landing. For them, the Yeti air crash may become a great case study for the importance of paying attention and professionalism.

The flight crew included a captain getting familiarization training with a new airport and a training captain. John highlights the many tasks being covered by the training captain and makes a case for the need for a third crew member in the cockpit.

The preliminary report shows that the training captain grabbed the wrong levers during approach. Neither pilot reacted well to the resulting flight issues. Human factors and poor communication are large contributors to the resulting crash.

Related documents:

• Yeti Airlines Preliminary Report
  
• NTSB Accident report KAL flight 801
  

This episode also includes discussion of the acting FAA administrator’s effort to put together a panel to study aviation safety. John, Greg and Todd talk about the types of people who need to participate to get an accurate picture of what is happening with aviation safety.

 
MTF...P2 

[Peetwo]

NTSB final report for SA226TC and Cirrus SR22 midair!! -   

Via Avweb:

NTSB Says Midair Pilot Overshot Pattern Turns

By Russ Niles -Published: April 1, 2023 Updated: April 2, 2023



The NTSB has cited airmanship and an air traffic control failure in the midair collision of a Cirrus SR22 and a Key Lime Air Swearingen SA226TC at Centennial Airport in Englewood, Colorado on May 12, 2021. The board found that the Cirrus pilot was going at least 50 knots over the recommended speed as he prepared to land. As a result, he overshot his turns from downwind to base to final by so much he ended up crossing the extended centerline of the adjacent parallel runway. That’s exactly where the Swearingen happened to be, and the Cirrus sliced through the twin’s fuselage. The Cirrus pilot activated the Cirrus Airframe Parachute System (CAPS) and settled about three miles from the airport while the cargo plane, missing a big chunk of its fuselage, landed “uneventfully,” according to the report. There were no injuries.

The report also says the Swearingen pilot had no idea the Cirrus was a factor because ATC didn’t advise him as is required when parallel runways are in operation. The two aircraft were being handled by different controllers on separate frequencies and the controller working the Cirrus did issue the required advisory “Had the controller issued an advisory, the pilot of the Swearingen may have been able to identify the conflict and maneuver his airplane to avoid the collision,” the report said.

Final report, via the NTSB: https://data.ntsb.gov/carol-repgen/api/A...103073/pdf & the Docket: https://data.ntsb.gov/Docket?ProjectID=103073

Media report from at the time:

And from blancolirio channel:

Also the FSD review the fatal PC12 inflight breakup NTSB prelim report:

MTF...P2 

[Peetwo]

Malaysia jet crash kills 10 people in Kuala Lumpur

Via SkyNews:

10 people have been killed in Malaysia after a private jet collided with a car and motorbike near the capital, Kuala Lumpur.

Officials say the Beechcraft jet was carrying six passengers and two crew when it lost contact with air traffic control and crashed into the vehicles on a stretch of highway near the airport.

Police say no emergency had been declared and the aircraft had been cleared to land four minutes before the crash site was observed.

Plus via YouTube:

And via ASN: https://aviation-safety.net/wikibase/343582

Narrative:

A Raytheon 390 Premier I impacted a highway in Elmina, Selangor, after a loss of control while on approach to Sultan Abdul Aziz Shah Airport (SZB/WMSA), Kuala Lumpur.
The two pilots, six passengers, a car driver and a motor cyclist on the ground perished.

Preliminary information indicates that the aircraft first contacted the SZB ATC at 14:47 local time, a landing clearance was given at 14:48, and three minutes later, the ATC noticed smoke coming from the crash site. Online photos and a car dashcam indicates the airplane impacted the ground at a high rate of descent, bursting into flames. The wreckage was highly fragmentated and spread over the highway and a wooded area.

P2 comment: There is a overview video footage in the above link which is also quite revealing - see: https://twitter.com/i/status/1692174661684167065

MTF...P2 

[Peetwo]

CHALK & CHEESE - TSBC v ATSB?

Via the TSBC:

News release

Investigation report: Collision with terrain at Goose Bay Airport, Newfoundland and Labrador

Dartmouth (Nova Scotia), 21 September 2023 — Today, the Transportation Safety Board of Canada (TSB) released its investigation report (A22A0067) into the 14 December 2022 collision with terrain involving a privately registered Piper PA-46-350P aircraft at Goose Bay Airport, Newfoundland and Labrador.

The TSB conducted a limited-scope, class 4 investigation into this occurrence to advance transportation safety through greater awareness of potential safety issues. See the Policy on Occurrence Classification for more information.

---

The TSB is an independent agency that investigates air, marine, pipeline, and rail transportation occurrences. Its sole aim is the advancement of transportation safety. It is not the function of the Board to assign fault or determine civil or criminal liability.

For more information, contact:
Transportation Safety Board of Canada
Media Relations
Telephone: 819-360-4376
Email: media@tsb.gc.ca

---

Definition Class 4 investigation:

Class 4 occurrence

A class 4 occurrence may have some important consequences. It may involve fatalities or serious injuries. There may be a small release of dangerous goods. There is moderate to minor damage to property and/or the environment. The occurrence attracts public interest within the immediate region or province/territory. The likelihood of identifying new safety lessons and of advancing transportation safety by reducing risks to persons, property, or the environment is low.

Basically this is the equivalent of an ATSB 'short' investigation.

To begin, this TSBC investigation took 9 months and 7 days to complete. Read the investigation webpage - HERE. 

Investigator-in-charge



Murray Hamm joined the TSB in 2010 as a Regional Senior Technical Investigator in the Air Investigations Branch at the Dartmouth office, Nova Scotia. Prior to that, he worked as a contracted employee for the 3 Canadian Forces Flying Training School (3 CFFTS) at the Southport Aerospace Centre located near Portage La Prairie, Manitoba, and held the position of Fixed Wing Chief Engineer.

Mr. Hamm has more than 25 years of aviation experience working for several fixed wing and rotary wing operations as a licensed Aircraft Maintenance Engineer. He has also enjoyed recreational flying as a private pilot, and as a glider student pilot.

The accompanying news release is short and to the point, relying totally on the professionalism of the IIC (above) to compose an excellent final report with solid lessons to be learnt - see HERE.

Compare that to this load of Popinjay inflicted bollocks...  : POPINJAY TO THE RESCUE!!?? 

MTF...P2 

[Peetwo]

Shocking Kingair C90 crash Brazil??

Via AirLive: https://airlive.net/news/2023/10/05/a-be...e_vignette

A Beechcraft C90GTi King Air aircraft (PS-JCO) has crashed into a hangar at Bom Futuro Airport in Brazil.

The accident took place when the KingAir aircraft was taking off, it began to tilt to the left, touched the left wing to the ground and headed towards the hangar.

MTF...P2