Cessna 150 and 152 Landing-Gear Concerns: Nose Fork and Main-Gear Structure
Landing-gear findings need a component-specific description. the records distinguish an early Cessna 150 nose-fork cracking concern from main-gear spring or fitting corrosion and wear in the relevant structural inspection material. These do not have identical applicability or authority.
_03.jpg){kind=link}
Nose fork versus main-gear structure
The nose-fork issue is tied to affected earlier configurations and time-in-service conditions. The main-gear issue belongs to the relevant SID-covered families. The table preserves those distinctions instead of combining them into a claim that every 150 or 152 has a single recurring landing-gear defect.
| Issue ID | Title | Affected Scope | Failure Mode | Detection / Prebuy Clues | Legal / OEM Status | Conditional Applicability Rule | Reference |
|---|---|---|---|---|---|---|---|
| KI-008 | Main landing-gear spring/fitting corrosion and wear | SID-covered 150/152 families. | Landing-gear springs and attach fittings require corrosion/structural inspection with aging. | Review SID records; inspect gear spring surfaces, attach fittings and prior corrosion removal/repairs. | OEM SID | Environment drives corrosion interval | [1] |
| KI-011 | Nose gear fork cracking | Affected Cessna 150-series earlier nose-gear fork/configuration and time-in-service conditions. | Earlier nose-gear fork/configuration can crack and requires recurrent/event inspection. | Verify fork P/N/configuration and AD compliance; inspect/NDT as required. | FAA AD - mandatory | Affected earlier fork/configuration installed | [2] |
| KI-008 | Main landing-gear spring/fitting corrosion and wear | SID-covered 150/152 families. | Landing-gear springs and attach fittings require corrosion/structural inspection with aging. | Review SID records; inspect gear spring surfaces, attach fittings and prior corrosion removal/repairs. | OEM SID | Environment drives corrosion interval | [1] |
.jpg){kind=link}
What to request in a prebuy review
Ask the inspecting mechanic to identify the component involved, the observed condition and the publication used to assess it. A generic statement that the landing gear was checked can leave uncertainty about which structure, fittings or nose assembly received attention. Repairs and replacements also need their own records.
The gear-system overview explains the relationships among main gear, nose gear, steering and shimmy dampener. The brake page covers another connected system. A ground-handling symptom cannot identify its cause from these overviews alone.
Applicability and history
The aircraft's damage and alteration history can change the research required. Establish the current installation rather than assuming that a component matches the factory configuration. For float-equipped aircraft, the landplane's wheel and nose-gear assumptions are not the applicable configuration description.
Use the damage-history guide to connect an inspection finding with prior repairs and supporting documents. Historical completion of a maintenance action does not establish present condition. This reference supplies no crack limit, repair method or return-to-service finding; those decisions require the applicable controlled information and qualified assessment.
.jpg){kind=link}
Keep the finding and authority separate
Describe the observed condition first, then identify the publication used to assess it. The existence of an AD or SID does not establish that its failure mode is present, and a physical discrepancy can require assessment even when it is not the subject of this particular issue record. This separation makes the prebuy report more useful than a checklist that merely counts matched issue numbers.