# N101UC: not currently registered

- Registered now: No (not in the FAA registry file). The mark may be reserved or free to assign
- Earlier aircraft: 1
- Last cancelled: June 26, 2000
- FAA registry: https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=101UC
- Page: https://openairdocs.org/aircraft/N101UC

## Aircraft that carried N101UC

- [Cancelled 2000-06-26](https://openairdocs.org/deregistered/N101UC-2000-06-26): Aerospatiale AS 355 F ECUREUIL, S/N 5186. Triennial form not returned. Owner: [Rts Helicopter Services Corp](https://openairdocs.org/faa-owner/RTS%20HELICOPTER%20SERVICES%20CORP), [Oklahoma City, OK](https://openairdocs.org/faa-place/OK/Oklahoma%20City)

## NTSB investigations on N101UC (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 NYC97LA058](https://openairdocs.org/ntsb/NYC97LA058), Mar 5, 1997: Aerospatiale AS-355F (N101UC), Washington, PA, substantial damage. Probable cause: The malfunction of a cyclic servo which resulted in a cyclic hard over at a hover.
- [NTSB SEA92LA029](https://openairdocs.org/ntsb/SEA92LA029), Oct 29, 1991: Aerospatiale AS355F1 (N101UC), Billings, MT, substantial damage. Probable cause: THE UNLATCHING AND SUBSEQUENT OPENING INFLIGHT OF THE LEFT-REAR ENGINE COWL DOOR. A FACTOR CONTRIBUTING TO THE ACCIDENT WAS THE FAILURE OF COMPANY MAINTENANCE PERSONNEL TO EXECUTE THE MANUFACTURER'S…
- [NTSB ATL88IA171](https://openairdocs.org/ntsb/ATL88IA171), May 13, 1988: Aerospatiale AS-355-F (N101UC), Reidsville, NC, incident, minor damage

## FAA accident and incident reports on N101UC (6)

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [Accident 19970305002189A](https://openairdocs.org/incident/19970305002189A), Mar 5, 1997: Aerosp AS355F (N101UC), Washington, PA, Substantial damage. Maintenance flight, repositioned to heli pad. Applied collected pitch for takeoff, rolled onto left side. (.19) on March 5, 1997, at 1215 eastern standard…
- [Incident 19960125002789I](https://openairdocs.org/incident/19960125002789I), Jan 25, 1996: Aerosp AS355F1 (N101UC), Monongahela, PA, Minor damage. Narrative: while practicing simulated single engine landings (run on) forward portion of port skid tube (from forward crosstube forward) separated from…
- [Incident 19941220046009I](https://openairdocs.org/incident/19941220046009I), Dec 20, 1994: Aerosp AS355F1 (N101UC), Pittsburgh, PA. Heard loud bang enroute diverted to Pittsburgh. Cargo doors separated. Indicates door not secured prior to flight.
- [Accident 19911028054699A](https://openairdocs.org/incident/19911028054699A), Oct 28, 1991: Aerosp AS355F (N101UC), Billings, MT, Substantial damage. Engine service door opened in flight. Was severed by contact with main rotors. Crew unaware. Bulletin not complied.
- [Incident 19910925048339I](https://openairdocs.org/incident/19910925048339I), Sep 25, 1991: Aerosp AS355F (N101UC), Billings, MT. Right engine fire warning after takeoff. Precautionary landing. Repaired broken wire at fire detector terminal.
- [Incident 19880512015299I](https://openairdocs.org/incident/19880512015299I), May 12, 1988: Aerosp AS355F (N101UC), Reidsville, NC, Minor damage. Tail rotor assembly separated at the gear box in flight. Made safe autorotation. Inadequate service inspections.

---
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.