CEN15LA138 · Air Tractor Inc AT 602
Frontier Air Tractor Inc AT 602 · Accident during takeoff
From Slaton Municipal Airport (F49) to Oakley Municipal Airport (KOEL)
Event
- NTSB case
- CEN15LA138
- 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
Air Tractor Inc AT 602
- Aircraft type
- Air Tractor AT-602
- 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
- N602PB
- Operator
- Frontier
- Onboard fatalities
- Unknown
- Route
- From Slaton Municipal Airport (F49), Slaton, TXTo Oakley Municipal Airport (KOEL), Oakley, KS
- Aircraft age
- About 2 years (built 2013)
- 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
- Defining eventThe 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
- Miscellaneous/other
- 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
- Aircraft › Aircraft handling/service
- Personnel issues › Experience/knowledge
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot, who had 3 hours of flight time in the agricultural airplane, was taking off on the planned cross-country flight, which was the first flight after the installation of a digital engine data monitor (EDM) on the airplane 6 days previously. The pilot reported that the initial takeoff seemed normal but that, halfway down the runway, red warning lights illuminated on the EDM. Although he reported that he thought the airspeed was low, the pilot was able to climb the airplane to 150 ft. The airplane lost altitude, and the pilot landed in a field. The landing gear dug into the soft dirt, and the airplane nosed over and came to rest inverted. The pilot added that, although he added full throttle, the engine never developed full power.
Examination of the airplane did not reveal any anomalies that would have prevented the engine from producing normal power. A review of the airplane's maintenance records showed that the EDM was installed under a supplemental type certificate, which included instructions and initial setup and installation checklists. However, a completed copy of neither the setup nor installation checklists were found in the records. The maintenance entry noted that ground runs and leak checks were completed, and no defects were noted.
Review of the EDM data revealed two files that contained engine starts; one from 3 days before the accident flight and one from the accident flight. The first data file showed that the engine propeller rpm reached a maximum of 950 rpm, indicating that this was a ground run and that the engine power setting was not increased above flight idle. During the accident flight, the engine propeller rpm reached a maximum of 1,730 rpm at an engine torque of 1,304 ft-lbs. Although the pilot said he advanced the throttle to obtain full power, a review of the EDM data revealed the torque was below its maximum value and was reduced several times during the flight.
Postaccident examination revealed that the EDM's engine operating range for the propeller was correctly set at the maximum 1,700 rpm; rpm readings above 1,700 would have been indicated by red warning lights. Based on the information, it is likely that the aircraft manufacturer set the maximum propeller rpm higher than 1,700 rpm (using the airplane's analog instruments), allowing the propeller rpm to exceed 1,700 rpm, which resulted in the red lights illuminating, as reported by the pilot. If maintenance personnel had followed the initial setup/installation checklists that were included in the installation instructions for the EDM, they likely would have identified that the maximum propeller rpm was not set properly and corrected it. The accident is consistent with the pilot reacting to the EDM's warning indications, likely due to his lack of experience in the airplane make and model.
Probable cause
Maintenance personnel’s improper installation of the engine data monitor (EDM), which was not in accordance with the supplemental type certificate instructions and resulted in engine warning indications and the pilot’s subsequent reaction to the warning indications due to his lack of experience with the EDM and airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN15LA138
- Event ID
- 20150206X02838
- Case number
- CEN15LA138
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 4403d04c5f6df94a1bdf2e0ce3bdc68547b080d02f878463ca4c9068f7a57d0a; retrieved 2026-09-16T02:04:28.784Z.