LAX87FA300 · Globe GC-1B
Globe GC-1B · Accident: in flight collision with terrain/water while maneuvering
From Porterville Municipal Airport (PTV) to an unrecorded destination
Event
- NTSB case
- LAX87FA300
- 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
Globe GC-1B
- Aircraft type
- Globe GC-1
- 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
- N80806
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Porterville Municipal Airport (PTV), Porterville, CATo not recorded
- 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 terrain/water
- 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 › Planning/decision, improper
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS FLYING OVER SHARPLY RISING TERRAIN IN A CANYON IN A MOUNTAINOUS AREA. THERE WAS INSUFFICIENT ROOM IN THE CANYON TO MANUEVER THE AIRCRAFT. THE PILOT REPORTED THAT HE HAD MAINTAINED AN AIRSPEED JUST ABOVE A STALL WHILE ATTEMPTING TO FLY THROUGH THE CANYON. THE AIRCRAFT IMPACTED TREES THEN THE TERRAIN WHERE THE TERRAIN ROSE ABRUPTLY. DENSITY ALTITUDE COMPUTED FOR THE 5,300 FT MSL ACCIDENT SITE ELEVATION WAS OVER 10,400 FT MSL. THE AIRCRAFT WAS ABOUT 24 POUNDS OVER MAX GROSS WEIGHT AT TAKEOFF. THE PILOT'S LAST BIENNIAL FLIGHT REVIEW WAS MORE THAN NINE YEARS BEFORE THE ACCIDENT. THE PILOT STATED THAT THERE WERE NO PRE-IMPACT MALFUNCTIONS OR FAILURES. HOWEVER, THE AIRCRAFT HAD NOT HAD AN ANNUAL INSPECTION SINCE JAN 1985.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX87FA300
- Event ID
- 20001213X31834
- Case number
- LAX87FA300
- 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: 8943094caf0e6fefe0f02725e91656a8888a12ebadb535484a4541604c3cf785; retrieved 2026-09-21T04:02:28.192Z.