elihoole/asrs-aviation-reports huggingface dataset:
Date: 201202
Flight conditions: VMC
Weather elements / visibility: Clear
Light: Dawn
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Commercial
Human factors: Fatigue; Situational Awareness
Anomaly: Other Fatigue
Detector: Person Flight Crew
Result: General Work Refused
Contributing factors: Company Policy; Procedure; Human Factors
Primary problem: Human Factors

Narrative: At 17:00L; contacted to report to the Airport ASAP to serve on 'Field Standby' to ferry a B777.  While driving to the airport; a two hour drive; I was in contact with scheduling that the auto traffic was heavy.  When I arrived at flight operations; I was told the flight was canceled but never informed.  I sat 'field standby' until 23:30L; then went to my car and drove home.  Arriving home at 03:00L; took a shower; and went to sleep at 04:00L.  The crew desk woke me at 07:00L; three hours of sleep after a full day of driving (300 miles) and assigned me a flying seat assignment leaving fourteen hours later.  I refused based on fatigue; they should have reviewed my schedule and called a few hours later; thereby DOUBLING my sleep.  I felt too exhausted and decided it was UNSAFE to be awake all day; to again drive two hours and then occupy the flying seat to [an international destination].




Synopsis: A Reserve First Officer was awakened after three hours of sleep by Crew Scheduling to be assigned a trip 14 hours in the future.  The trip is declined due to fatigue.
Date: 201812
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Windshear
Light: Daylight
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Time Pressure
Second reporter function: Captain; Pilot Flying
Anomaly: Inflight Event / Encounter Weather / Turbulence; Inflight Event / Encounter Unstabilized Approach; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Executed Go Around / Missed Approach; Flight Crew Diverted; Flight Crew Landed in Emergency Condition
Contributing factors: Company Policy; Procedure; Weather
Primary problem: Weather

Narrative: We were used off field standby to fly from ZZZ. The weather at ZZZ was forecast to be gusty but well within limits. No alternate was planned. Upon arriving at ZZZ the active runway was switched and tower reported strong tailwinds during the arrival that shifted to a headwind at 500-200 ft. The Captain conducted the approach and we elected to go around due to wind shear and being unstable. After established on downwind approach informed us that several previous aircraft had also been unable to land. We discussed our options and set a bingo fuel. We elected to divert after the next two aircraft went missed approach. We declared min fuel immediately. We landed uneventfully with 3000 lbs of fuel.


Second narrative: [Report narrative contained no additional information.]


Synopsis: Air carrier flight crew reported windshear on approach causing them to divert.
Date: 201908
Local time of day: 1201-1800
Location: DEN.Airport, CO
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B DEN
ATC / advisory: Tower DEN
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Fatigue; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: Company Policy; Human Factors
Primary problem: Company Policy

Narrative: Failed to fully configure aircraft. Both of us were focused on the aircraft in front of us; talking about the fact that he wasn't moving off the runway fast enough. Focused on that; we forgot to put gear down and complete configuration. Received the gear horn descending through 1;000 ft. with flaps 20. It took us a second or two to realize what just happened. I looked down and saw our altitude of 870 ft. and called for a go-around. Tower asked the reason and I replied that we weren't fully configured. They questioned us to make sure it wasn't their fault that we were too close but it wasn't their fault. Normal go-around followed by normal approach and landing. Just exhausted; I came off 2 full days off with decent sleep but only slept about 2 hours during the overnight. Eliminate stand-ups; the continuous duty-periods of them go completely against everything we know about fatigue; circadian rhythm; etc.




Synopsis: Captain reported fatigued resulted in a go around due to aircraft not being properly configured.
Date: 201702
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Exterior Pax/Crew Door
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Flying; Captain
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Object
Detector: Person Gate Agent / CSR
When detected: Pre-flight
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: After aircraft arrived [at the gate]; and apparently while it was unoccupied; the aircraft rolled forward and caused cosmetic damage to door 1L when door 1L contacted the jet bridge during the movement. No one on our flight was aware of the movement and the door damage until customer service tried to close the door and found that the door couldn't be moved due to it being held in place by the jet bridge. Maintenance was called and the departure delayed. Maintenance came and the door was freed and it was determined that the damage was only cosmetic to the interior seal and the door cover on the lower aft edge of the door. Door was operated several times and sealed correctly. Item was put on MEL; and the flight departed.


Second narrative: [Report narrative contained no additional information.]


Synopsis: The flight crew of a B737 reported that while parked at the gate; the aircraft rolled forward and the entry door made contact with the jet bridge.
Date: 201708
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight phase: Takeoff / Launch
Aircraft component: Electronic Flt Bag (EFB)
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Company Policy; Procedure
Primary problem: Aircraft

Narrative: The FOM requirement to secure the tablet in your flight kit when a securing device is inoperative is incompatible with the electronic checklists on said tablet. With one inoperative EFB mount; the Pilot Monitoring is required by FOM to stow their EFB in their flight kit during critical phases of flight. It is obviously impossible to read the Normal Checklist on the tablet in this state. As paper checklists are no longer carried in the airplane; this adds needless complexity to the operation. The FOM says mounts are available in maintenance bases. ZZZ maintenance advises they are out. Put the paper Normal Procedures checklists back in the airplanes fleet wide. Ensure EFB securing devices are available in maintenance bases in a timely fashion.




Synopsis: CRJ-200 Captain reported that without paper checklists; the requirement to stow the EFB when the EFB mount is inoperative leaves no Normal Checklist available.
Date: 202108
Local time of day: 0601-1200
Location: DFW.Airport, TX
Flight conditions: VMC
Light: Daylight
Aircraft: Medium Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B DFW
ATC / advisory: Tower DFW
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Ambiguous

Narrative: While crossing the threshold at Vref; a loss of speed and slight roll was encountered; similar to that of mild wake turbulence. Power was added in a timely fashion to arrest descent and neither horizontal; vertical; or speed stability was lost. The GPWS called 'don't sink; don't sink.' The approach remained stable so the landing was continued. We uneventfully touched down safely in the touchdown zone and exited on a high-speed taxiway short of B intersection.




Synopsis: Air carrier First Officer of medium transport reported encountering wake turbulence shortly before touchdown at DFW airport.
Date: 201907
Local time of day: 1201-1800
Location: JFK.Airport, NY
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28R Cherokee Arrow All Series
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Descent
Airspace: Class B JFK
ATC / advisory: TRACON N90
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Procedure
Primary problem: Ambiguous

Narrative: During an ATC assigned descent from 6;000 feet to 4;000 feet along V16 heading southbound; at approximately 8 NM from JFK VOR I saw an object (presumably a drone) with a green light on it go past my left wing. It was very close; I estimate approximately 10 feet off of my wing. I passed it as I was descending through 5;800 feet.




Synopsis: PA28R pilot reported encountering a drone while on an airway near JFK airport.
Date: 202004
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class D ZZZ
Aircraft component: Reciprocating Engine Assembly
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: After an uneventful flight we were returning to ZZZ. We were in contact with ZZZ Approach flying at 4500 ft.. About 11-12 miles out on an approximate 240 course we were cleared to start the descent. I reduced power to about 2300 RPM and started a slow descent.  At about 2200 ft.  we were handed off to Tower and told to make straight in for [Runway XX]. About 4 minutes later and 5 miles out; just as we were cleared to land [Runway XX]; we experienced a nearly total loss of power. At that time we were flying at about 1300 ft. and at 100 MPH. Without any obvious warning engine RPM fell from about 2100-2200 RPM to 1000 RPM. The power loss was quick without any unusual engine sounds. At the time engine carb heat was already pulled and boost pump was on; mixture setting was full rich. I was unable to get the engine to produce enough power to sustain altitude and performed an uneventful landing on the dry concrete river bed. There were no injuries to myself or one other passenger and the aircraft did not sustain any damages.Engine was successfully restarted on the ground about an hour and a half following the landing. Once the aircraft was moved to the airport; aircraft was started and taxied on its own power to the tied down area. Further examination of the engine and fuel systems will be performed.Preliminary examination of the engine did not reveal any problems. There was about an hour and a half reserve of fuel at the time of the incident. The current theory is that we experienced a nearly total loss of power due to accumulation of carb ice. Weather conditions at ZZZ at the time were: sky clear; visibility 10+; 22C; 37% relative humidity; wind at about 2 kts from NNW.It is possible that I pulled carb heat too late and enough ice accumulated by that point to cause the loss of RPM. Additionally I believe that I made a serious error in judgement deciding to descend this low while being relatively far away from the airport. If I were to stay at about 2500 ft. I would have been able to make the airport even after a drastic engine power loss. Additionally there would have been more time to allow carb ice to melt. As it happened; it took about 2 minutes from the onset of engine power loss to landing.




Synopsis: Pilot reported landing in a concrete creek bed after engine failure.
Date: 201410
Local time of day: 1801-2400
Location: LAF.Airport, IN
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: SR20
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Final Approach
Airspace: Class D LAF
ATC / advisory: Tower LAF
Second aircraft: SR20
Reporter organization: FBO
Reporter function: Instructor
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Commercial
Human factors: Other / Unknown
Second reporter function: Single Pilot
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Me and my student were doing night landings. The traffic pattern was fairly busy as [the college] has many students doing training. We were told to follow traffic ahead on the downwind. Me and my student had the airplane in sight and reported it to tower. They cleared us for the option. The other aircraft involved was to follow us on the downwind. He reported us in sight and was also cleared for the option. When we were on final approach to the runway; tower tells the other aircraft to go around. I saw my student looking up a little bit and I look up and see the other aircraft that should've been following us about 100ft above us. I was able to talk with the other pilot and we could not work out how he ended up on top of me. Tower didn't not sound frantic or distressed about the event.


Second narrative: I had been cleared for final with traffic in sight upon reaching short final ATC advised me to go around and then proceed with a right traffic pattern I had no knowledge of the near miss until I was on the ground and the pilot of the other aircraft approached me and informed me of the situation ATC did not advise me of any near miss situation in the air


Synopsis: Two local flight school aircraft experienced a near mid air collision when the pilot of the trailing aircraft did not identify and follow the proceeding aircraft. ATC called for a go-around to separate the conflict.
Date: 201603
Local time of day: 1201-1800
Location: MMU.Airport, NY
Flight conditions: VMC
Aircraft: Gulfstream V / G500 / G550
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class D MMU
ATC / advisory: Tower MMU
Second aircraft: Skyhawk 172/Cutlass 172
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft Y on VFR transition from the south to northwest climbing to 2;000 feet. Aircraft X IFR cleared for takeoff. Aircraft Y was on a more northerly track than I anticipated and flew in close proximity to Aircraft X opposite direction; each aircraft passing to the right of each other. I failed to issue traffic or preventive instructions to either aircraft due to my lack of attention to the radar scope. Aircraft Y was advised of the jet passing off his right. Pilot replied 'In sight; no factor'. Aircraft X declared RA with departure control. I can only attribute this inattention to a preoccupation with recent unrelated occurrences and current and personal life events.I have requested to be released from Local Control duties until such time as Management and I feel confident enough for me to safely resume responsibility for the position.




Synopsis: ATC reported a VFR transition aircraft and an IFR departure aircraft that passed close enough for one aircraft to receive an RA.
Date: 201507
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing; Final Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Workload
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Ground Event / Encounter Other / Unknown
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: General Evacuated
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On short final after gear extension; there was a smell similar to fireworks. As we were getting near the ground; I initially thought it was coming in from outside. The flight attendant called when we were a few hundred feet AGL; which I assumed meant she smelled it; as well. The FO took the call; and relayed to me the message back to me on rollout that there was visible smoke and smoke smell in the cabin. Hearing this; I advised ATC and called back to the FA to confirm and talk to her personally. She recommended an evacuation upon my query; and I asked her to wait for my call before beginning the evacuation. Told tower about smoke; and our intention to evacuate. Ran through the Evacuation checklist with the FO; and evacuated. Miraculously; no one was hurt or injured. We stayed with the aircraft once the passengers were safely escorted to the terminal via bus.


Second narrative: [Report Narrative Contained No Additional Information.]


Synopsis: CRJ-700 flight crew reported smelling smoke on short final which was observed and confirmed by the Flight Attendant. They evacuated the aircraft after landing.
Date: 202202
Local time of day: 1201-1800
Location: MHK.Tower, KS
Flight conditions: VMC
Weather elements / visibility: 10
Aircraft: Cessna Aircraft Undifferentiated or Other Model
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Descent
Airspace: Class D MHK
ATC / advisory: Tower MHK
Second aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Student and I were performing right-hand traffic patterns for Runway 03 at MHK. ATC instructed us to follow a [light twin] on our way to land. Visual contact was maintained with the [light twin] until they did a full stop and departed the runway. As my student was turning base to final; we noticed an aircraft that ATC had not warned us about approximately 200-300 ft. away from us. I took control of the aircraft in order to perform evasive action. My first priority was to get away from the aircraft; then to re-enter the downwind when it was safe to do so. Specifically; the power was advanced to full; the aircraft was positioned in a way to climb away from the conflict aircraft; and flaps were retracted per the published go-around procedure.According to ATC transmissions; the conflict aircraft (I believe it was a low-wing complex aircraft) was performing a practice instrument approach and was supposed to report when they were passing the FAF; which they apparently did not. I am unsure if the conflict aircraft ever saw us.As far as I am aware; my student (Pilot Flying) and I (Pilot Monitoring) were in good physical and mental shape at the time of the incident; and I first noticed the conflict aircraft as I was visually scanning the final approach corridor as we were preparing to turn final. Initially; my student could not see the conflict aircraft due to blind spots inherent with the model of the aircraft.




Synopsis: Cessna Flight Instructor reported an NMAC with another light aircraft on approach to MHK airport.