# NTSB NYC04LA061: Cirrus Design SR-22, N344CD, College Park, MD, January 22, 2004 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: January 22, 2004, 10:30 local (15:30 UTC) - Place: College Park, MD - Coordinates: 38.983333, -76.926109 - Nearby events: https://openairdocs.org/map.md?lat=38.9833&lon=-76.9261&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report January 24, 2005 - Report: Approved by Office Director - Parties: FAA - NTSB case key (mKey): 58672 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC04LA061 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/58672/pdf - Page: https://openairdocs.org/ntsb/NYC04LA061 ## Probable cause The loss of hydraulic fluid due to chaffing of a brake line by a strut fairing rivet, resulting in the failure of the braking system. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Airframe/component/system failure/malfunction, landing - roll - hydraulic system,line - chafed (cause) - Loss of control - on ground/water, landing - roll - landing gear,normal brake system - failure - On ground/water collision with object, landing - roll - object - airport sign/marker ## Analysis As the airplane touched down on the runway 15, the pilot applied the brakes and the left brake pedal did not respond. The airplane veered off the right side of the runway, proceeded into a grass area, where the left wing struck a VASI assembly before coming to rest upright. Examination of the airplane revealed a small hole in the left landing gear brake line. Further examination of the brake line revealed chafing marks created by a rivet, which was on a strut fairing bracket located adjacent to the brake line. During the airplane's most recent annual inspection, completed about 3 months prior to the accident, chafing was noted on the brake line, and the line was replaced. The strut fairing was installed on the airplane about 1 month prior to the accident. At the time of the strut fairing installation, no chaffing of the brake line was noted. ## Factual narrative On January 22, 2004, at 1030 eastern standard time, a Cirrus SR-22, N344CD, was substantially damaged while landing at the College Park Airport (CGS), College Park, Maryland. The certificated private pilot was not injured. Visual meteorological conditions prevailed, and an instrument flight rules flight plan was filed for the business flight, which originated at the Atlantic City International Airport, Atlantic City, New Jersey. The flight was conducted under 14 CFR Part 91. According to the pilot, as the airplane touched down on runway 15, a 2,607-foot long asphalt runway, the pilot applied the brakes. The left brake pedal did not respond, and the airplane veered off the right side of the runway. The airplane proceeded into a grass area, and the left wing struck a VASI assembly before coming to rest upright. Examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed a small hole in the left landing gear brake line. Further examination of the brake line revealed chafing marks created by a rivet, which was on a strut fairing bracket located adjacent to the brake line. During the airplane's most recent annual inspection, which was completed on October 29, 2003, chafing was noted on the brake line, and subsequently the line was replaced. On December 29, 2003, maintenance personnel replaced the left main landing gear fairing assembly and standoff. No chaffing of the brake line was noted. According to a representative of the airplane manufacturer, no further problems with chaffing of brake lines were identified with other airplanes after the accident. The airplane manufacturer subsequently issued a mandatory Service Bulletin on April 8, 2004, which contained instructions for brake line inspections and installation of anti-chafe spacers to the upper and lower nut-plate clips on the lower strut fairings. ## Aircraft - Registration: [N344CD](https://openairdocs.org/aircraft/N344CD), registered now, S/N 0156, built 2002 (OpenAirDocs) - Reported make and model: Cirrus Design Corp. SR-22 - Registry model: [Cirrus Design SR22](https://openairdocs.org/model/cirrus-design-sr22) (registry code 2130001) (OpenAirDocs) - Registry engine: [Continental IO-550 series](https://openairdocs.org/engine/continental-io-550-series) (registry code 17042, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 0156 - Airframe hours: 700 - Engines: Continental IO-550 210 horsepower reciprocating - Damage: Substantial damage - Flight: Business, Part 91 - Registered owner: Cirrus 22 Partners LLC - Airworthiness certificate: Standard, Normal - Last inspection: Annual, October 29, 2003, 50 hours before - Departed: ACY, Atlantic City, NJ - Destination: CGS, College Park, MD - Flight plan: IFR - Airport: CGS, College Park Airport, runway 15, 2,607 × 60 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 48; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, valid medical--no waivers/lim.; last flight review December 8, 2002; seat: left; flight hours: 890 total, 420 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: 230° at 12 knots - Visibility: 10 statute miles - Lowest ceiling: 10,000 ft overcast - Temperature: 41 °F, dew point 21 °F - Altimeter: 29.81 inHg - Observed at: DCA, 10 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20040122001039A](https://openairdocs.org/incident/20040122001039A), Jan 22, 2004: Cirrus SR22, College Park, MD, Substantial damage. (-23) On January 22, 2004 at approximately 10:20 EST, a Cirrus SR22, registered as N344CD, sustained substantial damage to its left wing after landing and roll… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.