DFW05CA233 · Israel Aircraft Industries 1124
Israel Aircraft Industries 1124 · Accident: on ground/water collision with object during landing
From Brownsville South Padre Island International Airport (BRO) to New Braunfels National Airport (BAZ)
Event
- NTSB case
- DFW05CA233
- 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
- Unknown
- 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
- Visual Meteorological Cond
Israel Aircraft Industries 1124
- Aircraft type
- Israel 1124
- 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
- N349MC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Brownsville South Padre Island International Airport (BRO), Brownsville, TXTo New Braunfels National Airport (BAZ), New Braunfels, TX
- 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
- Landing · landing roll
- 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
- On ground/water collision with object
- 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
- Object › Animal(s)
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 4,995-hour airline transport rated pilot reported that the nose wheel assembly of the 8-passenger turbo fan airplane collapsed following an on-ground collision with a coyote during the landing roll on Runway 17 (a 5,364-foot long by 100-foot wide asphalt runway) during a dark night visual approach. The public airport was not equipped with a perimeter fence to keep wild life away from the airport. The pilot was able to maintain the airplane on the runway until the airplane came to a complete stop in the upright position with the collapsed nose landing gear. The 2 crewmembers and the 8 passenger were able to egress from the airplane unassisted. There was no fire.
Probable cause
The airplane's collision with a coyote during the landing roll. A contributing factor was the prevailing night conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW05CA233
- Event ID
- 20051011X01614
- Case number
- DFW05CA233
- 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, coordinates. 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: db2966dc418c2210f49692c5b8a5e0c237cacde08b0eb26ee0c208976a544e73; retrieved 2026-09-18T14:58:53.944Z.