# N612CB: 2025 Cirrus Design SF50 - Status: Valid registration - Airframe: [Cirrus Design SF50](https://openairdocs.org/model/cirrus-design-sf50) (registry code 2130010, 7 seats) - Engine: [Williams FJ33-5A](https://openairdocs.org/engine/williams-fj33-5a) (registry code 66015) - Data sheets: [TCDS A00018CH](https://openairdocs.org/tcds/A00018CH) (Cirrus Design Corporation), [TCDS E3GL](https://openairdocs.org/tcds/E3GL) (Williams International Company L.L.C.) (OpenAirDocs) - Serial number: 0633 - Year built: 2025 - Type: Fixed wing single engine - Engine type: Turbo-fan - Airworthiness: Standard, normal - Airworthiness date: March 12, 2025 - Certificate issued: March 27, 2025 - Expires: March 31, 2032 - Mode S code: A7F660 - Registered owner: [Hb Aviation LLC](https://openairdocs.org/faa-owner/HB%20AVIATION%20LLC) - Location: [Lilesville, NC](https://openairdocs.org/faa-place/NC/Lilesville) - Owner type: LLC - Owner's area on the map: 34.9874° N, 79.9330° W: Placed by OpenAirDocs at the center of ZIP code 28091, within about 5 miles (OpenAirDocs). The owner's mailing address, not where the aircraft is based - FAA registry: https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=612CB - Page: https://openairdocs.org/aircraft/N612CB From the FAA registry file of October 24, 2026. ADs below are matched by the registry's airframe and engine model codes. They may apply; each AD's applicability can narrow it by serial number, part number or installed equipment. This is not a compliance determination. ## ADs that may apply (OpenAirDocs): 3 in force ### Matched by airframe (Cirrus Design SF50) - [AD 2023-04-20](https://openairdocs.org/ad/2023-04-20): Auto Flight System · Cirrus Design SF50. Effective Mar 21, 2023 - [AD 2020-03-50](https://openairdocs.org/ad/2020-03-50): Communications · Cirrus Design SF50. Effective Jun 11, 2020 - [AD 2019-08-51](https://openairdocs.org/ad/2019-08-51): Flight Controls · Cirrus Design SF50. Effective Jun 17, 2019 ### Matched by engine (Williams FJ33-5A) None in force. ## Information bulletins (advisory) None matched. ## NTSB investigations None matched to N612CB. ## NTSB investigations on N612CB not matched to an aircraft (3) 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. - [NTSB ERA11CA039](https://openairdocs.org/ntsb/ERA11CA039), Oct 28, 2010: Cessna 172P (N612CB), Tampa, FL, substantial damage. Probable cause: The student pilot's failure to maintain directional control during a short-field takeoff. - [NTSB ANC04LA029](https://openairdocs.org/ntsb/ANC04LA029), Feb 21, 2004: Cessna 172P (N612CB), Lutz, FL, substantial damage. Probable cause: The student pilot's misjudged landing flare, which resulted in a hard landing and subsequent collapse of the nose landing gear. - [NTSB ATL02LA172](https://openairdocs.org/ntsb/ATL02LA172), Sep 20, 2002: Cessna 172P (N612CB), Lutz, FL, substantial damage. Probable cause: The pilot's failure to maintain visual lookout and clearance during taxi, which resulted in an on-ground collision with a building. ## FAA accident and incident reports None matched to N612CB. ## Reports on N612CB not matched to an aircraft (5) They name N612CB, but no registry record covers the date, the aircraft registered then was built later, or the report describes another aircraft. - [Accident 20101028051299A](https://openairdocs.org/incident/20101028051299A), Oct 28, 2010: Cessna 172P (N612CB), Lutz, FL, Substantial damage. During takeoff roll from runway 32 the aircraft veered left, departed the runway, and crashed into two vehicles in a parking lot. Cockpit controls confirm… - [Accident 20040221013709A](https://openairdocs.org/incident/20040221013709A), Feb 21, 2004: Cessna 172P (N612CB), Tampa, FL, Substantial damage. (-23) On February 21, 2004, at 1330 EST, a Cessna 172, N612CB, registered to helicopter structure and maintenance, collided with the ground at Tampa north aero… - [Incident 20030126014069I](https://openairdocs.org/incident/20030126014069I), Jan 26, 2003: Cessna 172P (N612CB), Tampa, FL, Minor damage. (-23) While taxiing aircraft and trying to avoid another, aircraft's propeller contacted a runway light causing damage to prop. No injuries. Owner of aircraft… - [Accident 20020919025159A](https://openairdocs.org/incident/20020919025159A), Sep 19, 2002: Cessna 172P (N612CB), Tampa, FL, Substantial damage. (.19) On September 19, 2002, at 2100 eastern daylight time, a Cessna 172P, N612CB, registered to helicopter structural and maintenance, inc., and operated by… - [Incident 19810125012449I](https://openairdocs.org/incident/19810125012449I), Jan 25, 1981: Cessna 414 (N612CB), West Chicago, IL, Minor damage. Pilot lost control and ran off runway due to left brake failure. Reservoir was dry and o ring leaking. ## Service difficulty reports None filed for this aircraft. Matched to this aircraft by N-number and event date, checked against the reported serial number, make and model. ## STCs that may be installed (OpenAirDocs) (3) Approved for this aircraft's airframe or engine model, in force first, then newest. The registry doesn't record which STCs an aircraft has; its records do. ### Approved for the airframe (Cirrus Design SF50) - [STC SA09887AC](https://openairdocs.org/stc/SA09887AC): Installation of an Avionica MK-III mini Quick Access Recorder (QAR) and optional 4G or LTE Avionica Cellular Module (avCM. Aircraft Systems and Manufacturing Inc - [STC SA04615CH](https://openairdocs.org/stc/SA04615CH): BasicMed 6-place occupancy restriction. CIRRUS DESIGN CORPORATON - [STC SA00401BO](https://openairdocs.org/stc/SA00401BO): Installation of a SkyTrax100B UAT receiver. Avidyne Corporation ## Related - Other Cirrus Design SF50 aircraft: https://openairdocs.org/model/cirrus-design-sf50/aircraft.md - The Williams FJ33-5A engine: https://openairdocs.org/engine/williams-fj33-5a.md --- 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.