Rescue 26 down?
Join Date: Aug 2007
Location: Australia
Posts: 10
Likes: 0
Received 0 Likes
on
0 Posts
Helo 1,
I take it vh-pvk is an AS365, if that's the case will be interesting to see how it all works out.
As I understand it (sure I'll be corrected if I'm wrong) the customer specified the contract requirement was for a single type interim platform for standardisation of procedures & practices etc...
I take it vh-pvk is an AS365, if that's the case will be interesting to see how it all works out.
As I understand it (sure I'll be corrected if I'm wrong) the customer specified the contract requirement was for a single type interim platform for standardisation of procedures & practices etc...
Join Date: Jun 2006
Location: Perth, Australia
Posts: 94
Likes: 0
Received 0 Likes
on
0 Posts
Having read through this thread, I find nothing concrete as to what happened to the 412 to make it carry out its heavy landing. Personally not interested in the CHC vs CareFlight BS, just professionally interested in what went wrong so that I can learn from it.
Anybody (who actually knows what happened) care to elaborate on the event so that this forum can gain experience from it. Hate to have it happen to me and then someone say ''Óh yeah, that happened to Rescue 26 last year
Anybody (who actually knows what happened) care to elaborate on the event so that this forum can gain experience from it. Hate to have it happen to me and then someone say ''Óh yeah, that happened to Rescue 26 last year
Join Date: Feb 2008
Location: saigon
Posts: 17
Likes: 0
Received 0 Likes
on
0 Posts
Spoke to a friend who witnessed the incident and he said it (from a plank drivers point of view) was hovering and then started to spin and landed hard, he also said that there was no noticeable damage. We were both drinking at the time he told me this story so sorry if it is a little wrong, but he seems to be the only reliable source or witness to this event I know.
But there is a new 412 there vh-bzh (I think thats what it said)
But there is a new 412 there vh-bzh (I think thats what it said)
Join Date: Feb 2005
Location: Oz
Posts: 23
Likes: 0
Received 0 Likes
on
0 Posts
Could it have anything to do with this?
Airworthiness Directives; Bell Helicopter Textron Model 204B, 205A, 205A-1, 205B, 210, 212, 412, 412CF, and 412EP Helicopters
AGENCY: Federal Aviation Administration, DOT.
ACTION: Final rule; request for comments.
SUMMARY: This amendment adopts a new airworthiness directive (AD) for the specified Bell Helicopter Textron (Bell) model helicopters. This action requires certain checks and inspections of each tail rotor blade assembly (T/R blade) at specified intervals and repairing or replacing, as applicable, any unairworthy T/R blade. This amendment is prompted by three failures of a T/R blade occurring during flight and a recent incident of a cracked T/R blade discovered during a scheduled visual inspection. The actions specified in this AD are intended to detect damage to a T/R blade that could lead to cracking of a T/R blade and subsequent loss of control of the helicopter.
SUPPLEMENTARY INFORMATION: A proposal to amend 14 CFR part 39 to include an AD for the specified model helicopters was published in the Federal Register as Docket No. FAA-2006-26219, Directorate Identifier 2004-SW-49-AD on November 2, 2006 (71 FR 64484). That Notice of Proposed Rulemaking (NPRM) was prompted by eight reports of fatigue cracking of T/R blades installed on Bell Model 212 and 412 helicopters (three failures on the Bell Model 212 and five failures on the Bell Model 412) with a blade assembly, part number (P/N) 212-010-750-009, - 105, and -107. Six of the cracks initiated between blade stations 30 to 33.5; one crack initiated at blade station 21.9; and one crack initiated at blade station 27.6. Three of these T/R blades failed during flight and all were installed on Bell Model 412 series helicopters. In one of the in-flight failures, the T/R blade failed due to a fatigue crack that initiated in the blade skin from a nick .060 inches long by .008 inches deep. The initial damage was above the maximum allowable damage limit for the blade skin provided in the maintenance manual. That failed blade had accumulated 1,478 hours time- in-service (TIS). In another in-flight failure, a section of the T/R blade separated from the helicopter during cruise flight at 5,500 feet. The helicopter was reported to have violently turned down and to the left. The helicopter "leveled out" at approximately 1,000 feet before setting down in the water. The blade failed due to a cracked stainless steel leading edge spar that originated from a corrosion pit .001 inches deep. The corrosion area extended .003 inches along the surface of the origin location. That blade had accumulated 4,643 hours TIS. In the third in-flight failure, sanding on the spar and chem-milling was found during a post-accident investigation. The crack had initiated at blade station 21.9 and the blade had accumulated 1,232 hours TIS.
Airworthiness Directives; Bell Helicopter Textron Model 204B, 205A, 205A-1, 205B, 210, 212, 412, 412CF, and 412EP Helicopters
AGENCY: Federal Aviation Administration, DOT.
ACTION: Final rule; request for comments.
SUMMARY: This amendment adopts a new airworthiness directive (AD) for the specified Bell Helicopter Textron (Bell) model helicopters. This action requires certain checks and inspections of each tail rotor blade assembly (T/R blade) at specified intervals and repairing or replacing, as applicable, any unairworthy T/R blade. This amendment is prompted by three failures of a T/R blade occurring during flight and a recent incident of a cracked T/R blade discovered during a scheduled visual inspection. The actions specified in this AD are intended to detect damage to a T/R blade that could lead to cracking of a T/R blade and subsequent loss of control of the helicopter.
SUPPLEMENTARY INFORMATION: A proposal to amend 14 CFR part 39 to include an AD for the specified model helicopters was published in the Federal Register as Docket No. FAA-2006-26219, Directorate Identifier 2004-SW-49-AD on November 2, 2006 (71 FR 64484). That Notice of Proposed Rulemaking (NPRM) was prompted by eight reports of fatigue cracking of T/R blades installed on Bell Model 212 and 412 helicopters (three failures on the Bell Model 212 and five failures on the Bell Model 412) with a blade assembly, part number (P/N) 212-010-750-009, - 105, and -107. Six of the cracks initiated between blade stations 30 to 33.5; one crack initiated at blade station 21.9; and one crack initiated at blade station 27.6. Three of these T/R blades failed during flight and all were installed on Bell Model 412 series helicopters. In one of the in-flight failures, the T/R blade failed due to a fatigue crack that initiated in the blade skin from a nick .060 inches long by .008 inches deep. The initial damage was above the maximum allowable damage limit for the blade skin provided in the maintenance manual. That failed blade had accumulated 1,478 hours time- in-service (TIS). In another in-flight failure, a section of the T/R blade separated from the helicopter during cruise flight at 5,500 feet. The helicopter was reported to have violently turned down and to the left. The helicopter "leveled out" at approximately 1,000 feet before setting down in the water. The blade failed due to a cracked stainless steel leading edge spar that originated from a corrosion pit .001 inches deep. The corrosion area extended .003 inches along the surface of the origin location. That blade had accumulated 4,643 hours TIS. In the third in-flight failure, sanding on the spar and chem-milling was found during a post-accident investigation. The crack had initiated at blade station 21.9 and the blade had accumulated 1,232 hours TIS.
Guest
Join Date: Oct 2005
Posts: 64
Likes: 0
Received 0 Likes
on
0 Posts
SuperSleuth, yes an AS365 has been bought in on the NSW Ambulance contract. By the paint scheme it looks like the Dauphin from the Mackay CQ Rescue contract. It is now operating in Orange. Must of run out of spare 412s in the country.
Guest
Join Date: Oct 2005
Posts: 64
Likes: 0
Received 0 Likes
on
0 Posts
looks like I have to stand corrected here, what a difference two days makes. Now apparently no helicopter in the Central West for the rest of the week. Probably doesn't matter, the weather is ****e.
Cloud hangs over helicopter service - Local News - News - General - Central Western Daily
Cloud hangs over helicopter service - Local News - News - General - Central Western Daily
