CHI92LA012 · Rockwell 112YC
Rockwell 112YC · Accident: airframe, component or system failure on approach
From Cherry Capital Airport (TVC) to an unrecorded destination
Event
- NTSB case
- CHI92LA012
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Rockwell 112YC
- Aircraft type
- Rockwell 112
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N4603W
- Operator
- Raymond A. Pedersen · private individual
- Onboard fatalities
- Unknown
- Route
- From Cherry Capital Airport (TVC), Traverse City, MITo not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR pattern final
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Maintenance, major repair, not performed
- Pilot in command › Operation with known deficiencies in equipment, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACCIDENT AIRPLANE LANDED WITH THE NOSE LANDING GEAR PARTIALLY EXTENDED. THE PILOT STATED, 'I APPROACHED GLIDE SLOPE I LOWERED THE GEAR. I GOT GREEN LIGHTS ONLY ON THE TWO MAIN GEAR AND NO NOSE GEAR.' THE PILOT PERFORMED A GO AROUND AND REQUESTED CLEARANCE TO A CLEAR AREA IN ORDER TO ASCERTAIN THE NATURE OF THE LANDING GEAR PROBLEM. WHEN ALL ATTEMPTS TO LOWER THE NOSE LANDING GEAR WERE UNSUCCESSFUL THE PILOT ORDERED HIS PASSENGER INTO THE REAR SEAT AND LANDED ON THE SOD ADJACENT TO THE RUNWAY. FEDERAL AVIATION ADMINISTRATION (FAA) INSPECTORS FOUND PREEXISTING STRUCTURAL AND SHEET METAL DAMAGE IN THE NOSE AREA OF THE AIRPLANE DURING A POST ACCIDENT INSPECTION.
Probable cause
THE PILOT'S FAILURE TO PERFORM A MAJOR REPAIR AND CONTINUED OPERATION OF THE AIRPLANE WITH KNOWN DEFICIENCIES.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI92LA012
- Event ID
- 20001212X18271
- Case number
- CHI92LA012
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 25738dd0053abbbe54b30b6329b14f38069c889445af230338b2a1e147663507; retrieved 2026-09-23T03:36:10.018Z.