# N331NW: 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: April 30, 2025
- FAA registry: https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=331NW
- Page: https://openairdocs.org/aircraft/N331NW

## Aircraft that carried N331NW

- [Cancelled 2025-04-30](https://openairdocs.org/deregistered/N331NW-2025-04-30): Airbus Industrie A320-211, S/N 318, built 1992. Owner: [Delta Air Lines Inc](https://openairdocs.org/faa-owner/DELTA%20AIR%20LINES%20INC), [Atlanta, GA](https://openairdocs.org/faa-place/GA/Atlanta)

## NTSB investigations on N331NW (4)

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 DCA12CA043](https://openairdocs.org/ntsb/DCA12CA043), Nov 10, 2011: Airbus Industrie A320 211 (N331NW), Minneapolis, MN, substantial damage. Probable cause: In-flight collision with birds during initial climb, which resulted in substantial damage to the aircraft.
- [NTSB CHI08IA022](https://openairdocs.org/ntsb/CHI08IA022), Oct 21, 2007: Airbus Industrie A320-211 (N331NW), Fargo, ND, incident, minor damage. Probable cause: The failure of the Brake and Steering Control Unit, which allowed the nose landing gear to turn to the 90-degree position.
- [NTSB CHI95IA342](https://openairdocs.org/ntsb/CHI95IA342), Apr 28, 1995: Airbus Industrie A320-211 (N331NW), Minneapolis, MN, incident, no damage. Probable cause: inadequate design of the fly-by-wire flight control system which allowed false signals from the sidestick transducer units to generate uncommanded rolls.
- [NTSB CHI95IA138](https://openairdocs.org/ntsb/CHI95IA138), Apr 27, 1995: Airbus Industrie A320-211 (N331NW), Washington, DC, incident, no damage. Probable cause: the pilot's excessive use of the flight controls during the landing approach, the company's disregard of information provided by the airplane manufacturer, and the company's failure to identify a…

## FAA accident and incident reports on N331NW (3)

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.

- [Incident 20100723038789I](https://openairdocs.org/incident/20100723038789I), Jul 23, 2010: Airbus Indu A320-211 (N331NW), Las Vegas, NV, Minor damage. On arrival at Las Vegas, the #3 main tire recap separated from the tire body. The right inboard flap leading edge was damaged, the honeycomb panel at the top…
- [Incident 20080301832719I](https://openairdocs.org/incident/20080301832719I), Mar 1, 2008: Airbus A320211 (N331NW), Memphis, TN, No damage. (-23) Nwa flight #1749 departed kmsp enroute to mmcz. Shortly after level off the first officer noticed a fuel imbalance greater than that allowable. The…
- [Incident 20071022830949I](https://openairdocs.org/incident/20071022830949I), Oct 22, 2007: Airbus A320211 (N331NW), Fargo, ND, Minor damage. (-23) At approximately 1907 CDT northwest flight 1432, a normal passenger flight from msp to FAR was landing on runway 18. The crew had received several fault…

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