# Incident 20100624038309I: Bombardier CL-600-2B19, Minneapolis, MN, June 24, 2010

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: June 24, 2010, 19:28 local time
- Place: Minneapolis, MN
- Airport: Minneapolis-St Paul International/Wold-
- Damage: No damage
- Phase of flight: Takeoff: Climb Out
- Operating rules: Air carrier (Part 121)
- Operator: REXA
- Location: 44.8820° N, 93.2218° W: Placed by OpenAirDocs at MINNEAPOLIS-ST PAUL INTL/WOLD-CHAMBERLAIN (MSP), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=44.8820&lon=-93.2218&mi=10
- Aircraft: N8775A, a cancelled registration (https://openairdocs.org/deregistered/N8775A-2024-01-16) (OpenAirDocs)
- Registry model: Bombardier CL-600-2B19 (registry code 1390008, https://openairdocs.org/model/bombardier-cl-600-2b19) (OpenAirDocs)
- Registry engine: GE CF34-3B1 (registry code 30070, https://openairdocs.org/engine/ge-cf34-3b1) (OpenAirDocs)
- Reported make and model: BOMBARDIER CL-600-2B19
- Reported engine: GE CF34-3B1
- People aboard: 39
- Fatal injuries: 0
- Other injuries: 0
- Pilot flight hours: 0 total, 0 in this make and model, 0 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20100624038309I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

PINNACLE FLIGHT 3931, CRJ-200 MBS TO MSP REPORTED A RIGHT HAND MAIN LANDING GEAR INDICATION PROBLEM. AIRCRAFT LANDED AT MSP WITHOUT INCIDENT ON RUNWAY 30R.CORRECTIVE ACTION:INSPECTED AND CLEANED R/H MLG UPLOCK AND PROX SENSOR. ALSO COMPLETED A GEAR SWING, INDICATION WAS NORMAL.

## Other reports on N8775A (1)

Matched to the same aircraft by N-number and date.

- [Incident 20060618013309I](https://openairdocs.org/incident/20060618013309I), Jun 18, 2006: Cndair CL6002B19 (N8775A), Wichita, KS. (-23) On June 18, 2006, pinnacle airlines flight 2826, at 1455 local time, aircraft N8775A while enroute from minneapolis Minnesota, to Oklahoma city, diverted…

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. For accidents, the NTSB's own investigation is the fuller record.

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