Ransome Airlines Nord Aviation 262A-12 incident
Nord Aviation 262A-12 · Incident: airframe, component or system failure en route
From Newark, NJ to Providence, RI
Event
- NTSB case
- NYC82IA051
- 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
- Incident
- 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
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Nord Aviation 262A-12
- Aircraft type
- Nord 262
- 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
- N26210
- Operator
- Ransome Airlines
- Onboard fatalities
- Unknown
- Route
- From Newark, NJTo Providence, RI
- 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 135: Air Taxi & Commuter
- 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
- En route · climb to cruise
- 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
- Minor
Cause areas
- Propeller system/accessories, blade › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE CLIMBING THROUGH 7000 FT, THE AIRCRAFT BEGAN TO SHAKE VIOLENTLY. THE FIRST OFFICER CONFIRMED THAT THE SOURCE OF VIBRATION WAS THE RIGHT ENGINE. AN UNSUCCESSFUL ATTEMPT WAS MADE TO FEATHER THE PROP AFTER THE RT ENGINE WAS SHUT DOWN. THE AIRCRAFT CONTINUED TO VIBRATE SO THE CREW DECLARED AN EMERGENCY AND LANDED AT LAGUARDIA AIRPORT. THE NO. 2 PROP BLADE ON THE RT PROP HAD FAILED IN FATIGUE AND SEPARATED ABOUT 14 INCHES OUTBOARD OF THE HUB. THE FATIGUE CRACK INITIATED FROM AN AREA OF PITTING CORROSION THAT WAS COVERED BY THE ELECTRICAL DEICING BOOT. EXAMINATION OF THE BOOT AT THE FATIGUE ORIGIN OF THE BLADE DISCLOSED LOCALIZED OVERHEATING HAD OCCURRED WHICH DETERIORATED THE BOOT. THIS WAS IN THE AREA WHERE THE HEATING ELEMENT JOINS A BRAIDED WIRE BUNDLE. TOTAL TIME ON THE PROP WAS 1435 HOURS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC82IA051
- Event ID
- 20020917X02572
- Case number
- NYC82IA051
- 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: 59bf0d74efa8d10285e666d471349d83c607b8f3bf90f3b5ed77f080969493c2; retrieved 2026-09-18T21:11:21.365Z.