SEA03LA010 · Learjet 36A
Phoenix Air Learjet 36A · Accident: on ground/water collision with object during takeoff
From Astoria Regional Airport (KAST) to Astoria Regional Airport (KAST)
Event
- NTSB case
- SEA03LA010
- 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
- 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
Learjet 36A
- Aircraft type
- Learjet 36
- 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
- N546PA
- Operator
- Phoenix Air
- Onboard fatalities
- Unknown
- Route
- From Astoria Regional Airport (KAST), Astoria, ORTo Astoria Regional Airport (KAST), Astoria, OR
- 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
- Takeoff
- 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
- Destroyed
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 pilot (PIC) reported that during acceleration for takeoff (approximately V1 [takeoff decision speed]) the airplane collided with an elk. The PIC reported that after the collision, he applied wheel brakes and deployed the airplane's drag chute, however, the airplane continued off the departure end of the runway. The airplane came to rest in a marshy bog approximately 50 feet beyond the departure threshold. Currently, approximately 15,000 feet of the airport's perimeter is bordered with animal control fence. The airport recently received a FAA Aviation Improvement Program (AIP) Grant that will provide funding for an additional 9,000-feet of fence. Airport officials stated that the fencing project should be completed by summer of 2003. At the completion of the project, game control fencing will encompass the entire airport perimeter. The U.S. Government Airport/Facilities Directory (A/FD) contains the following remarks for the Astoria Regional Airport: "Herds of elk on and in the vicinity of airport..."
Probable cause
Collision with an elk during the takeoff roll. Factors include dark night VFR conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA03LA010
- Event ID
- 20021205X05569
- Case number
- SEA03LA010
- 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: 775e6223efa980e9b8fbc2e645312478904232ee268e3d1bf7481ce1359bd5bf; retrieved 2026-09-22T09:50:21.044Z.