FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW95FA238 · Smith LONG-EZ

12 Jun 1995 · Cloudcroft, NM, United States

Smith LONG-EZ · Accident: in flight collision with object while maneuvering

From Alamogordo White Sands Regional Airport (ALM) to Roswell Air Center Airport (ROW)

Report a problem

Event

NTSB case
FTW95FA238
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
1 · 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
General aviation
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

Smith LONG-EZ

Aircraft type
Smith LONG-EZ
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
N86PD
Operator
Unknown
Onboard fatalities
Unknown
Route
From Alamogordo White Sands Regional Airport (ALM), Alamogordo, NMTo Roswell Air Center Airport (ROW), Roswell, NM
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 91: General Aviation
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
Maneuvering
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
In flight collision with object
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Clearance, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE LINEMAN AT ALAMOGORDO AIRPORT REPORTED ADDING 28 GALLONS OF 100LL AVGAS TO THE FUEL TANKS. THE AIRCRAFT TOOK OFF WITH TWO MEN (APPROXIMATELY 195 POUNDS EACH PLUS PERSONAL ITEMS). THE AIRCRAFT WAS OBSERVED FLYING LOW OVER HIGH ROLLS, NEW MEXICO AND EAST TOWARDS PINEY WOODS, NEW MEXICO. WITNESSES IN PINEY WOODS REPORTED TO THE STATE POLICE THAT 'THE AIRCRAFT WAS CIRCLING SO LOW THAT THEY THOUGHT IT WAS GOING TO LAND.' THE AIRPLANE WAS NEXT OBSERVED AT THE TOP OF THE VALLEY IN THE MOUNTAIN PASS VILLAGE OF CLOUDCROFT, NEW MEXICO, WHERE A WITNESS REPORTED THAT IT OVERFLEW THE VILLAGE 'AT A VERY LOW ALTITUDE AND MISSED THE TOP OF MY BUILDING BY 30 FEET.' THE AIRPLANE WAS OBSERVED SEVERAL TIMES MAKING ABRUPT STEEP BANK HEADING CHANGES. ONE WITNESS REPORTED THAT 'THE PLANE WAS ON ITS SIDE AND THE WINGS WERE PERPENDICULAR TO THE GROUND.' THE AIRPLANE COLLIDED WITH A TALL PINE TREE AND SUBSEQUENTLY IMPACTED THE GROUND. THE ELEVATION AT THE ACCIDENT SITE WAS 8,665 FEET AND THE CALCULATED DENSITY ALTITUDE AT THE TIME OF THE ACCIDENT WAS 11,900 FEET.

Probable cause

THE PILOT'S FAILURE TO MAINTAIN CLEARANCE FROM TREES. FACTORS WERE THE PILOT EXCEEDED THE ALLOWABLE MAXIMUM GROSS WEIGHT OF THE AIRPLANE, THE RISING TERRAIN, AND HIGH DENSITY ALTITUDE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW95FA238
Event ID
20001207X03687
Case number
FTW95FA238
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: 3f41e55d1c4d5585828ce071b28de1d1934891947bb4a028eb04db7c4d787a62; retrieved 2026-09-20T23:44:35.966Z.