Nature Air Flight 144
Cessna 208 Caravan · Stalled and crashed on climb-out over rising terrain
From Islita Airport (PBP) to Juan Santamaría International Airport (SJO)
Event
- NTSB case
- CEN18FA063
- 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
- Event fatalities
- 12 · all aircraft and ground
- Ground fatalities
- Unknown
- Occupants
- 12
- Survivors
- 0
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 0 serious · 0 minor (NTSB)
- 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
- Airline
- 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
Cessna 208 Caravan
- Flight
- 5C144
- Aircraft type
- Cessna 208
- 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
- TI-BEI
- Operator
- Nature Air
- Onboard fatalities
- 12
- Route
- From Islita Airport (PBP)To Juan Santamaría International Airport (SJO)
- Aircraft age
- About 16 years (built 2001)
- 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
- Non-U.S., Commercial
- 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
- 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
- Aerodynamic stall/spin
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.
From the Wikipedia article
Nature Air Flight 144 crashed into terrain on 31 December 2017 shortly after takeoff from Punta Islita Airport in Nandayure, Guanacaste Province, Costa Rica, for a chartered domestic passenger flight to Costa Rica's capital San José killing all 12 people on board. The flight, with a planned duration of 40 minutes, was operated by Costa Rican regional airline Nature Air and the aircraft involved was a Cessna 208B Caravan manufactured in 2001. On board the aircraft were 10 passengers, mostly American tourists, and 2 pilots. An NTSB investigation later determined that the accident was caused by the aircraft entering an aerodynamic spin/stall that was the result of pilot error. Nature Air permanently ceased operations following the accident.
Accident flight
The flight was one of two that had been chartered by Backroads Travel Company and took off from the airport at Punta Islita, a small beach town on the Pacific coast of Costa Rica at 12:10 p.m local time. It was carrying 10 passengers, including two American families of tourists, plus two local pilots. The flight was destined for the Juan Santamaría International Airport in Costa Rica's capital San José where the passengers would connect with an international flight to return home to the United States. The accident aircraft had arrived late in Punta Islita due to strong winds and on the outbound leg landed at an intermediate point at the airstrip in Tambor where pilots waited for better weather conditions.
Seconds after departure, the aircraft swayed to the left. It then rolled, the wing clipped trees and the plane impacted rising terrain near the airport, exploded and burst into flames. The aircraft could not be contacted and was declared missing. Approximately at 12:30 p.m, emergency services near the airport received reports that the aircraft had crashed into the woods. Emergency service sent 20 vehicles, including ambulances and 45 firefighters. Tourists and locals who saw the crash also rushed to the crash site and assisted the rescue operation.
Photos published from Costa Rica's Ministry of Public Security revealed that the aircraft was pulverized on impact. The fire chief of Nandayure, Hector Chavéz, stated that the scene was a "total destruction". It crashed inverted with no survivors. By 07:00 p.m local time, rescuers had recovered all the victims of the flight.
Investigation and cause
Investigation
The Costa Rican Government opened an investigation into the cause of the crash on 1 January 2018. The investigation was conducted by Costa Rica DGAC. The United States National Transportation Safety Board (NTSB) was expected to assist the Costa Rican authorities in the investigation, as most of the passengers were of American origin. On 18 May, the GAC offered to delegate the investigation to the NTSB. The NTSB accepted the offer on 30 May 2018.
In the initial stage of the investigation, investigators cited mechanical failure, human factors, and adverse weather condition as the cause of the crash. Multiple reports gathered from eyewitnesses revealed that the weather conditions in Punta Islita were inclement. Gusts of 20 knots (37 km/h; 23 mph) were reported. Another witness stated that the aircraft flew too low. Enio Cubillo, head of the Costa Rican DGAC, stated that the investigation of Flight 144 would take months.
On 8 January 2018, Costa Rica's Organismo de Investigación Judicial (Judicial Investigation Organisation) raided the offices of Nature Air in Tobías Bolaños International Airport in Pavas and the Juan Santamaria International Airport in San José. They also raided the offices of the Costa Rica Dirección General de Aviación Civil in La Uruca as part of the investigation of the crash. At least 30 agents participated in the operation with the objective to obtain files on the pilots and on the Cessna 208 Caravan as well as the identities of those in charge of the maintenance and whoever authorized the flight.
In December 2019, two years after the crash, the NTSB released the final report on the accident. It had been caused by the following:
Text from the Wikipedia article “Nature Air Flight 144” (revision 1374419170, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
NTSB narrative
The two pilots were conducting a commercial charter flight to take 10 passengers to an international airport for connecting flights. The flight departed a nontower-controlled airport that was in a valley surrounded on all sides by rising terrain, with the exception of the area beyond the departure end of runway 21, which led directly toward the Pacific Ocean. The accident airplane was the second of a flight of two; the first airplane departed runway 3 about 15 minutes before the accident airplane and made an immediate right turn to the east/southeast after takeoff, following a pass in the hills over lower terrain that provided time for the airplane to climb over the mountains. Both a witness and surveillance video footage from the airport indicated that, 15 minutes later, the accident airplane also departed from runway 3 but instead continued on runway heading, then entered a left turn and descended into terrain. Analysis of the video determined that the airplane reached a maximum bank angle of about 75° and an airspeed below the airplane's published aerodynamic stall speed before impact.
Examination of the airplane was limited due to impact and postcrash fire damage; however, no defects consistent with a preimpact failure or malfunction were observed, and the engine exhibited signatures consistent with production of power during impact.
The captain was appropriately rated and had extensive experience in the accident airplane make and model. He had been employed by the accident operator for about a year in 2006 and had recently been re-hired by the operator; however, records provided by the operator did not indicate that he had completed all of the training and check flights required by the operator's General Operations Manual (GOM). The first officer was appropriately rated but had little experience in the accident airplane. The GOM also stated that pilots would receive additional, airport-specific training before operating to or from airports with special characteristics; however, the operator provided no listing of such airports, including the airport from which the accident flight departed. The pilots' experience at the departure airport could not be determined.
It is possible the psychiatric diagnoses in 2011 were correct and the pilot suffered from a number of conditions which can cause a variety of symptoms. However, given the extremely limited information, what his symptoms were around the time of the accident, whether they were being addressed or effectively treated, and what his mental state was at the time could not be determined from the available information. Therefore, whether or not the pilot's medical or psychological conditions or their treatment played a role in the accident circumstances could not be determined by this investigation.
There were no weather reporting facilities in the vicinity of the airport. Although the airport was equipped with two frames for windsocks, no windsocks were installed at the time of the accident to aid pilots in determining wind direction and intensity. Although a takeoff from runway 21 afforded the most favorable terrain since the airplane would fly over lower terrain to the ocean, it is possible that a significant enough tailwind existed for runway 21 that the pilots believed the airplane's maximum tailwind takeoff limitation may be exceeded and chose to depart from runway 3 in the absence of any information regarding the wind velocity. Performance calculations showed that the airplane would have been able to take off with up to a 10-kt tailwind, which was the manufacturer limitation for tailwind takeoffs.
The witness who saw the accident reported that he spoke with the pilots of both airplanes before the flights departed and that the pilots acknowledged the need to use the eastern pass in order to clear terrain when departing from runway 3. The reason that the flight crew of the accident airplane failed to use this path after takeoff could not be determined. It is likely that, after entering the valley ahead of the runway, with rising terrain and peaks that likely exceeded the climb capability of the airplane, they attempted to execute a left turn to exit the valley toward lower terrain. During the steep turn, the pilots failed to maintain adequate airspeed and exceeded the airplane's critical angle of attack, which resulted in an aerodynamic stall and impact with terrain.
Performance calculations using weights that would allow the airplane to operate within manufacturer weight and balance limitations at the time of the accident indicated that it was unlikely that the airplane would have had sufficient climb performance to clear the terrain north of the airport. However, the airplane would likely have had sufficient climb performance to clear terrain east of the airport had the crew performed a right turn immediately after takeoff like the previous airplane.
Probable cause
The flight crew's failure to maintain airspeed while maneuvering to exit an area of rising terrain, which resulted in an exceedance of the airplane's critical angle of attack and an aerodynamic stall. Contributing to the accident was the flight crew's decision to continue the takeoff toward rising terrain that likely exceeded the airplane's climb capability, the lack of adequate weather reporting available for wind determination, and the lack of documented training for an airport requiring a non-standard departure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
Wikipedia article: Nature Air Flight 144
- Article
- Nature Air Flight 144
- Revision
- 1374419170 · 2026-09-11 · retrieved 2026-09-18
- Wikidata
- Q47009401
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record CEN18FA063
- Event ID
- 20180101X94108
- Case number
- CEN18FA063
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
- Record
- Wikipedia article "Nature Air Flight 144" (page 56181483, revision 1374419170); merged with NTSB case CEN18FA063 (events / aircraft)
- Date
- Wikipedia infobox: date
- Place and country
- Wikipedia infobox: site
- Map position
- Wikipedia: Wikipedia article coordinates
- Aircraft, operator and route
- Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports); gaps and aircraft details from NTSB record CEN18FA063
- Operation
- airline flight number in the infobox
- Fatalities
- Wikipedia: Wikipedia infobox: aircraft fatalities
- Ground fatalities
- Wikipedia: not stated in the Wikipedia infobox
- Summary
- Wikipedia infobox: summary
Source notes (2)
- One occurrence in two sources, merged: the Wikipedia article "Nature Air Flight 144" and NTSB case CEN18FA063, matched by the same aircraft registration and date. For this event outside the United States Wikipedia's values are used where the two differ; each value names its source.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.