Jump to content
Aero Precision provides OEM part support for military aircraft operators across more than 20 aircraft

casey

Administrators
  • Content Count

    48
  • Joined

  • Last visited

  • Days Won

    4

casey last won the day on February 24

casey had the most liked content!

Community Reputation

5 Neutral

About casey

  • Birthday 11/20/1972

Personal Information

  • Website
    Http://www.c-130Hercules..net

core_pfieldgroups_2

  • First Name
    Casey
  • Last Name
    Comer
  • Gender
    Male
  • Location
    Dallas, GA

core_pfieldgroups_3

  • Occupation
    Aircraft Maintenance Manager

Recent Profile Visitors

3,996 profile views
  1. The New South Wales Rural Fire Service confirms three people have died after a C-130 heavy air tanker owned by Coulson Aviation crashed in Australia this afternoon. The aircraft was deployed to fires in the Snowy Mountains. They lost contact with the machine and the flight tracker stopped. “There’s no indication at this time what caused the accident,” NSW RFS commission Shane Fitzsimmons said in a press conference tonight. There were approximately four other aircraft in the area fighting the fire at the time. The weather has been hot, dry and windy with smoke and dust in the area. “It was another very difficult, aggressive fire day.” “We are deeply saddened to confirm there were three fatalities,” Coulson Aviation confirmed in a post on its Coulson Aviation – Next Gen Firefighting Facebook page. The aircraft had departed Richmond, NSW with a load of retardant and was on a firebombing mission. “The accident response team has been activated as well as local emergency services. Coulson Aviation will be sending a team to the site to assist in emergency operations. “Our thoughts and prayers are with the families of the three crew members onboard,” said the statement, signed “The Coulson Family. The NSW RFS reported on Twitter at 7:22 p.m. PST that it was investigating reports of a “serious incident” involving an aircraft in southern New South Wales. The NSW RFS media release states that contact was lost with a large air tanker working in the Snowy Monaro area. The wreckage has been located. There was a fireball associated with the crash, according to the NSW RFS spokesperson. “First and foremost, our thoughts and prayers are with the family of the three crew…and with Coulson Aviation, with whom we’ve had a long association.” New South Wales Premier Gladys Berejiklian said in a news conference that the crash “demonstrates the dangerous work being undertaken and demonstrates the conditions that our firefighters are working under. There were in excess of 70 aircraft being used today (Jan. 23 in Australia) alone. “Today is a stark and horrible reminder of the dangerous conditions that our volunteers and emergency services personnel across a number of agencies undertake on a daily basis.” Berejiklian said there were 1,700 volunteers and personnel working to control fires a number of fires across New South Wales on the day the plane crashed. Coulson grounded their large air tankers this afternoon in NSW and Victoria pending a review and out of respect to the families of the crew members, a NSW spokesperson said. No names are being released pending notification of next of kin. All three crew members were U.S. residents, Fitzsimmons said. Coulson Aviation representatives will be in Sydney, NSW within the next 24 hours. Coulson and the NSW RFS have worked together for the past four or five years and last year purchased a converted 737 air tanker from the Port Alberni-based aviation company. Coulson is contracted to operate and maintain that 737 for the Rural Fire Service, and also has a second 737 and second C-130 operating in the state of Victoria, Fitzsimmons said. View full record
  2. Please do not post any Export Control data on this site. WARNING -This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec. 2751 et seq.) or the Export Administration Act of 1979 (Title 50, U.S.C., App. 2401 et seq.), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.
  3. casey

    3756_A.jpg

    © 314FMS

  4. The Marine Corps determined that a corroded propeller blade that came off mid-flight was the cause of the July 10, 2017, crash of a KC-130T transport plane. That propeller did not go through proper maintenance the last time it was sent to an Air Force repair depot, which may have led to the damaged propeller remaining on the airplane that ultimately crashed and killed all 16 personnel onboard. The Marine Corps released a partially redacted Judge Advocate General Manual Investigation today, which found that “the investigation found the primary cause of this mishap to be an in-flight departure of a propeller blade into the aircraft’s fuselage. … The investigation determined that the aircraft’s propeller did not receive proper depot-level maintenance during its last overhaul in in September 2011, which missed corrosion that may have contributed to the propeller blade liberating in-flight,” according to a Marine Corps press release on the investigation. Marine Forces Reserve conducted the investigation and has made several recommendations for Naval Air Forces and for the Air Force to consider for their C-130 fleets. The Crash On July 10, 2017, a crew from reserve unit Marine Aerial Refueler Transport Squadron 452 (VMGR-452) departed their home station at Stewart Air National Guard Base in New York and flew to Marine Corps Air Station Cherry Point, N.C. Their mission for the day was to transport six Marines and a Navy corpsman assigned to 2nd Marine Raider Battalion from North Carolina to Naval Air Facility El Centro, Calif., where the special operations unit was set to conduct pre-deployment training. The aircraft departed Cherry Point at 2:07 p.m. Its last transmission to local air traffic control was at 3:46 p.m., and the last radar contact with the plane was at 3:49, when the plane was flying at 20,000 feet altitude, according to the JAGMAN. The Marine Corps investigation found that Blade 4 on Propeller 2 (P2B4, in the report) became unattached, struck the port side of the fuselage, cut straight through the interior of the passenger area of the plane and became lodged in the interior of the starboard side of the plane. This damage kicked off a series of events that led to Propeller 3 colliding with the starboard side of the fuselage and ultimately the plane breaking into three pieces mid-air. The cockpit and the rear of the fuselage crashed into two separate debris fields in a soybean field near Itta Bena, Miss. The middle section of the plane, where the passengers were located, further broke up in the air. Marine Corps leadership made clear there was nothing the crew or passengers could have done to prevent the mishap or save themselves once the propeller blade broke loose. Brig. Gen. Bradley James, commanding general of 4th Marine Aircraft Wing, which oversees the reserve KC-130T squadron, wrote in the investigation report that “the initial incident that started the cascading failure was the liberation of a blade from the #2 propeller assembly. The subsequent events quickly led to structural failure of the aircraft. Neither the aircrew nor anybody aboard the KC-130T could have prevented or altered the ultimate outcome after such a failure.” Pictures of the Marines and sailor who died in a KC-130T cargo aircraft on July 10, 2017. USMC Photos Killed in the crash were: Maj. Caine Goyette, an active duty Marine who was flying the plane the day of the crash, who the report found was current on all his certifications and had 2,614 hours of flight time in military aircraft; Capt. Sean Elliott, an active duty Marine who co-piloted the plane and had 822 hours of military aircraft flight experience; Gunnery Sgt. Mark Hopkins, Gunnery Sgt. Brendan Johnson, Staff Sgt. Joshua Snowden, Sgt. Owen Lennon, Sgt. Julian Kevianne, Cpl. Collin Schaaff and Cpl. Daniel Baldassare, who were part of the VMGR-452 crew; and Staff Sgt. Robert Cox, Staff Sgt. William Kundrat, Sgt. Chad Jenson, Sgt. Talon Leach, Sgt. Joseph Murray, Sgt. Dietrich Schmieman and Petty Officer 2nd Class Ryan Lohrey, who were assigned to 2nd Marine Raider Battalion. Maintenance Failures Though no one on the plane could have stopped the events that unfolded, the maintenance community could have prevented them. The investigation found a failure to inspect the propeller during its last depot maintenance period, as well as missed opportunities during squadron-level maintenance to potentially notice the corroded blade. The plane itself was 24 years old and was last in depot maintenance at Warner-Robbins Air Logistics Complex (WR-ALC) in Georgia in August 2011 for blade overhauls. The Air Force complex is manned by civilian employees who rework and overhaul propellers and is the sole source of this overhaul work for Navy and Marine Corps C-130s. According to the JAGMAN, the Navy and Marine Corps require C-130 propellers to undergo an overhaul every 5,000 to 6,000 flight hours. Investigators studying the plane wreckage found not only corrosion in the Blade 4 Propeller 2, but found anodize coating inside the corrosion pitting – which means the corrosion was there during the 2011 overhaul, and instead of removing the corrosion and fixing the blade, the coating was applied over the damaged blade. “Negligent practices, poor procedural compliance, lack of adherence to publications, an ineffective [quality control/quality assurance] program at the WR-ALC, and insufficient oversight by the [U.S. Navy], resulted in deficient blades being released to the fleet for use on Navy and Marine Corps aircraft from before 2011 up until the recent blade overhaul suspension at WR-ALC occurring on 2 September 2017,” reads the JAGMAN, referring to the September “Redstripe” standdown of all Navy C-130s until further blade inspections could be conducted. Twelve of the 16 total blades on the plane that crashed – four blades on each of four propellers – “were determined to have corrosion that existed at the time of their last overhaul at WR-ALC, proving that over the course of the number of years referred to above, that WR-ALC failed to detect, remove and repair corrosion infected blades they purported to have overhauled. … Thirteen of the sixteen blades on the [mishap aircraft] had other discrepancies proving that, over the same span of years referred to above, WR-ALC was deficient in the effective application of the following steps: anodization, epoxy primer and permatreat,” the JAGMAN continues. Though less severe than the failure at the Air Force depot, the report noted concerns with maintenance practices within the squadron earlier in 2017, in the months before the crash. According to the JAGMAN, the squadron failed to establish a formal process to track and perform the 56-day conditional manual inspections of the propeller blades that can be triggered when the plane is not used or when the blades are not rotated for 56 days. Due to a lack of a clear procedure, on at least two occasions in 2017 a conditional inspection was triggered, but the squadron believed that separate inspections met the requirement and therefore the maintainers did not do the manual blade inspection. However, the investigation notes that it could not be determined whether a manual inspection could have identified the damage to the blade that led to it becoming detached mid-flight and causing the crash. Recommendations In August 2017, a Navy engineering team conducted a process audit at Warner-Robbins Air Logistics Complex and found that, even though the Navy and Marine Corps have separate blade overhaul procedures and standards from the Air Force, the civilian workforce had failed to track which blades belonged to which service and therefore which maintenance standards to apply. Only about 5 percent of the blades belong to Navy and Marine Corps planes, but the Navy recommended creating a standard work flow process and the Air Force agreed to adopt all the Navy’s processes. The report also recommends that Warner-Robbins Air Logistics Complex maintain electronic records of all blade overhauls that can be kept permanently, compared to the paper records that are discarded after two years. It also recommends greater Navy oversight of Navy/Marine Corps overhauls at Warner-Robbins, blade overhauls at a more frequent interval than 5,000 hours, and additional clarity on the 56-day inspections. View original article: https://news.usni.org/2018/12/06/marine-corps-corroded-propeller-blade-that-broke-loose-caused-2017-kc-130t-crash
  5. Can anyone confirm the Reg/Lockheed Production number of the incident aircraft?
  6. A Pakistan Air Force (PAF) C-130 cargo aircraft crash landed at Nur Khan airbase in Rawalpindi on Friday. The aircraft caught fire after the hard landing and the pilot and the trainee pilot were reported safe by authorities. The PAF C-130 was on a routine training flight, said a spokesman for the service and added that the fire was extinguished and all crew members are safe. A board of inquiry has been ordered by Air Headquarters to ascertain the cause of the incident., added the PAF spokesman. The C-130, a US manufactured four-engine turboprop military transport aircraft, is the workhorse of the air force’s fixed-wing transport fleet. The tactical transport aircraft was inducted into the PAF in the early 1960s and has remained at the forefront of relief operations during natural calamities. Apart from transporting all manner of cargo, the aircraft is also used by paratroopers and special operation forces when performing airborne operations. Earlier in June, two pilots died when a PAF training aircraft crashed while landing at the Peshawar airbase. The plane was returning from a routine operational training mission, when it crashed during landing. In another accident, a Frontier Corps soldier was martyred and two others were injured when an Army helicopter crash-landed on the outskirts of Quetta. The helicopter was en route from Kohlu to Quetta and carrying an injured soldier. The soldier was being evacuated in an injured condition, however, he died when the helicopter made a crash landing. Members of the crew sustained minor injuries during the crash. View original article
  7. casey

    Birthdays?

    You're welcome. I retire 1 Oct. I certainly miss Bob he was a good friend and a member of the C-130 community. --Casey
  8. casey

    Birthdays?

    @Mt.crewchief Ken, I have added birthdays to the main page just below the member stats. --Casey
  9. After the database failure and having to rebuild the site, the URLs for some, probably most, pages changed. Fortunately, I was able to recover the majority of the site content which I am still working to restore. Unfortunately, the process to restore the content is a bit complex and it is taking me longer than I would like to straighten everything up. Sorry for the inconvenience. --Casey
  10. I have been working to restore the member profile field titles and data. I have made some progress but I have hit a roadblock. The following fields were not populated on my profile and there fore I do not know what their original titles were: core_pfield_2 core_pfield_4 core_pfield_8 core_pfield_9 core_pfield_10 core_pfield_11 core_pfield_12 core_pfield_13 If anyone has those fields complete and can determine what the title should be based on the data they contain, please let me know. In the meantime, I will see about restoring the profile cover photos. Thanks for bearing with me, I will get things back to normal soon. --Casey
  11. I have all the site content saved including the gallery images. The production number gallery and the members gallery have been restored. I will try to get the rest of the galleries taken care of this weekend. If there is something specific you are looking for, let me know and I'll take care of it first. It is a slow process but I will get it all restored in time. --Casey
  12. That's just it. Asking where someone is from based on their use of a word that is not common where you live is not derogatory. I did read Larry's comment (I think tiny's curiosity was aroused as you used a word much different than what we use to describe a system malfunction) and again, there is nothing derogatory about being curious about someone (where they are from.) The rest of his comments are clearly an attempt to placate you . I also understand that English is not everyone's native tongue and that underscores my point that we should not assume intent. Trust me, if I it appeared that Tiny was being derogatory toward you, I would have given him the same type of warning. We are happy to have you here, to have you contribute to the community and to help you where we can. With that said, please keep in mind that we all have the responsibility to keep our emotions in check and to not assume mistreatment when there is no objective evidence to support our stance. --Casey
  13. @tinyclark has been a member of this site since its inception and based on more than 10 years of history, it is a safe bet that he did not intend to insult you. I am sure that he knows the meaning of the word "snag" and does not need to look it up in the Oxford Dictionary. Furthermore, I am quite certain that one cannot find the answer to what he was curious about (Where are you from?) in a dictionary. Assuming the intent of another is never a good practice, neither is causing drama in our forums. You have been warned... --Casey
×
×
  • Create New...