elihoole/asrs-aviation-reports huggingface dataset:
Date: 201506
Local time of day: 1801-2400
Location: ZZZZ.ARTCC, FO
Flight conditions: VMC
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Descent
ATC / advisory: Center ZZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Fatigue; Human-Machine Interface
Anomaly: Deviation - Altitude Overshoot
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were descending on the arrival. The FO (PF) decided to hand fly; announced it; and disconnected the autopilot. As we were approaching level off; the aircraft started a slight left turn away from course. He said 'What's it doing?' and went up to the FCP to select a heading back to course; then he reselected NAV. The aircraft stayed in a slight left turn and as we approached our level off he made no effort to raise the nose. I said 'There's your altitude' as we passed through it; and he raised the nose to level off. We descended 200 - 300 FT below our assigned altitude. As he was correcting he responded; 'I forgot the motion was on!' meaning he forgot he was hand flying. Nothing was heard from ATC about the deviation. He managed to remember he was hand flying for the rest of the descent and approach.For some reason the FO decided to hand fly the arrival then promptly forgot he was doing it! This was our second leg of the night; and we were definitely on the back side of our body clocks. When you even remotely feel tired; let the automation be your friend.




Synopsis: MD11 First Officer forgot that he was hand flying the arrival and questioned why the aircraft started to turn and did not level off.
Date: 201312
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: Trailing Edge Flap
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Aircraft; Human Factors; Procedure; Weather
Primary problem: Ambiguous

Narrative: When I arrived at the aircraft; I noticed the flaps were left at 40. The aircraft was towed from Maintenance Hangar and a note left on center pedestal 'Do not move flaps due to ice on the wings.'  During the pre-flight I noticed about 3 inches of ice accumulation on the wing surface of both wings (mid chord to trailing edge). The flaps were left at 40 until the certified deicer deiced the aircraft wings and tail with Type 1. The certified deicer completed the deicing. I moved the flaps to 5 per the TPS. On takeoff we retracted the flaps on schedule. As we accelerated I noticed that we needed almost 3 units of rudder trim and still needed aileron trim to maintain heading. Once we leveled off I went to the back to check on the wings. By doing so I noticed the right TE Flap was not completely flushed up and 2 of the spoilers were out. We had no indications in the cockpit. The right TE flap was not up and not at 1; but the left flaps were viewed up. We declared an emergency and returned. Because of the unknown of structural damage we did the following procedure in the QRH; All flaps up landing. The landing was uneventful. Significant damage to the TE flap linkage.




Synopsis: B737-800 First Officer reports receiving an aircraft from Maintenance with ice on the wings and the flaps full down and a note not to move the flaps until the aircraft has been deiced. After de icing the flaps are set for takeoff and the flight departs. Once airborne the aircraft requires significant rudder and aileron trim to fly straight. A trip to the cabin by the First Officer reveals that the right TE flap is not fully retracted and that two spoilers are partially extended. An emergency is declared and the flight returns to the departure airport for flaps up landing.
Date: 202008
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Physiological - Other
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Just prior to departure; purser advised me the passenger in seat X5 [was] coughing; unmasked; not sure if he was unable or unwilling to wear a mask; and had just thrown up on himself.  I made the decision that the person was not suitable for a [long] flight and was to be removed.  The two passengers traveling with him had elected to stay behind and the GSC (Ground Security Coordinator) coordinated the removal of the three passengers.




Synopsis: Air carrier Captain reported that an ill passenger boarded and was not wearing a face mask. Captain decided to have passenger removed from flight due to length of the flight and passenger's condition.
Date: 201305
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb; Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Aircraft Auto Temperature System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Human factors: Physiological - Other
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed As Precaution; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: During the climb and initial leveloff the cockpit and forward cabin temperatures rose to uncomfortable levels (100 F to 120 F). I selected full cold on all cabin temp controllers with no effect noted.  I selected the cabin hot air valve off per flight manual reset procedure.  Within a few minutes temperatures dropped into uncomfortably cold levels in all cabins.  Aft and forward cabin temperatures were in the low forties with no ability to control the temperatures available.  This is [a] chronic issue with this aircraft as per the log history.  I contacted Dispatch and Maintenance.  Maintenance suggested a pack reset via recycle of pack circuit breakers.  Since this action required Captain's emergency authority; I advised Dispatch and Maintenance that we would divert to ZZZ regardless of whether or not this fixed the issue.  ZZZ was 45 minutes away so in the interest of safety of flight I reset the pack circuit breakers.  This provided no relief.  Temperatures remained uncontrollable from one extreme to the other.  An emergency was declared and we proceeded to ZZZ.  During the descent the lead Flight Attendant reported a burning electrical/oil odor in the forward cabin with no smoke noted.  No odor or smoke was noted in the cockpit.  I requested a follow up call if the odor worsened or smoke became evident.  An uneventful approach and overweight landing followed.  To our surprise operations was not aware of our divert.  We waited 10 to 15 minutes for a gate.  At the gate mechanics reported a burning oily smell lingering in the pack intake area.  An odor/smoke checklist was completed by the lead Flight Attendant and myself.




Synopsis: A319 Captain experiences uncomfortably hot temperatures in the cockpit and forward cabin during climb.  With the the Hot Air valve turned off uncomfortably cold temperatures result and the crew elects to divert to a suitable airport.  This was a chronic issue with this aircraft according to the maintenance history.
Date: 201510
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Second aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Government
Reporter function: Ground
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Provided Assistance
Contributing factors: Airport; Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: Aircraft X landed Runway XXR and exited onto occupied Taxiway. With an aircraft in position and holding on Runway XXL; the Local Controller asked Aircraft X to pull up right behind the other aircraft on Taxiway. I went back to working my traffic since the aircraft was not crossing at taxiway intersection. When I looked back at Locals traffic; an aircraft was midfield rotating; while Aircraft Y was rolling out Runway XXR; and Aircraft X's tail was still protruding over the hold position marking not clear of Runway XXR. There was no AMASS alert.I am not sure if Local saw that the aircraft had not pulled forward enough. Aircraft X had enough room to pull forward more.




Synopsis: Local Control cleared an aircraft for takeoff. Previous arrival's tail; on taxiway exit; had not cleared hold position marking.
Date: 202012
Local time of day: 1201-1800
Location: 2WA1.Airport, WA
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZSE
Second aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Reporter organization: Personal
Reporter function: Flight Engineer / Second Officer; Single Pilot
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Software and Automation
Primary problem: Human Factors

Narrative: We were flying east at 3;500 VFR and Aircraft X was 3;500 Westbound. We noticed the Aircraft X at very close range and made a turn to the right to avoid the aircraft. We had ADS-B and did not see the traffic and believe there is no coverage in this area. No ATC services were requested at the time.




Synopsis: A VFR Pilot reported they performed evasive maneuvers to avoid an opposite direction VFR aircraft flying at a wrong altitude for their direction of flight. The aircraft did not appear on their ADS-B.
Date: 202012
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 135 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Weather / Turbulence; Inflight Event / Encounter Unstabilized Approach
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: I as Pilot Flying; was initially on a stable approach descending to 3;500 ft. on base for [landing]. I had briefed a Flaps 22 landing. As I was turning base to final (a left turn) and starting further descent; the winds shifted and resulted in a loss of tailwind; and my airspeed increased in the turn. At that same time Tower told us to turn 10 degrees right I believe due to traffic. Through all of this; my approach became unstable with too steep a descent; and got [we] a GPWS sink rate alert. I immediately executed a go around. ATC issued a new clearance and we came back and landed without incident. Suggest some more insight; and different scenarios taught on Flaps 22 landings possibly during training. Because of the higher airspeed vs. Flaps 45; it seems there is an increased chance of unstable approaches; especially if the winds shift as in my case. I carried too much power on this approach and also got distracted with the instruction from Tower to turn opposite of my base to final turn.




Synopsis: EMB-135 First Officer reported executing a go-around after receiving a GPWS 'Sink Rate' alert on a visual approach associated with a wind shift.
Date: 201703
Local time of day: 0601-1200
Location: ZLA.ARTCC, CA
Light: Daylight
Aircraft: Small Transport
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZLA
ATC / advisory: Center ZLA
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness; Training / Qualification
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Airspace Structure; Chart Or Publication; Procedure
Primary problem: Procedure

Narrative: Aircraft X on a new OAPM (Optimization of Airspace and Procedures in the Metroplex) route should have been at 23000 feet. Adjacent controller reread the letter of agreement and realized their error.




Synopsis: ZLA Center Controller received an aircraft on an OAPM departure from an adjacent sector at the wrong altitude.
Date: 201807
Local time of day: 0601-1200
Location: BWI.Airport, MD
Light: Daylight
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E PCT
ATC / advisory: TRACON PCT
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
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Airspace Structure
Primary problem: Airspace Structure

Narrative: I have flown out of BWI on the TERPZ 6 to either OTTTO or RAMAY the last three weeks. Each time I have flown a 737-800 or MAX8. The first two times in the 737-800 we had to adjust our climb out speed below the ECON Schedule (which was around 300) to make the 17;000ft.; or above restriction at FOXHL (FMC warnings were received 'unable next altitude'). In the 737 MAX8; it was less. So by starting early to adjust our profile we were able to meet the restriction. It appears like a trend that heavy 737-800 aircraft in summertime will have a hard time meeting the climb restriction; and if you do not catch it soon enough you may not make the FOXHL restriction.[Suggestion].In the Departure Section of the SID add a note. If departing the TERPZ 6 to OTTTO or RAMAY be aware that high gross weights and hot temperatures may not allow you to climb via the FMC ECON Speed and meet the 17;000ft.; or above restriction at FOXHL.




Synopsis: B737-800 First Officer reported that departing out of BWI; the aircraft is unable to make the 17000ft. restriction at FOXHL on TERPZ 6 departure.
Date: 201909
Local time of day: 0601-1200
Location: MIA.Airport, FL
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B MIA
ATC / advisory: Tower MIA
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Human factors: Communication Breakdown; Distraction; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was finishing up securing the galley. I did hear a chime go off. I never heard 'flight attendants prepare for departure' myself; the number one and a cabin jumpseat rider were all standing up when the plane started taking off. The carts were not secure! All 3 of us stood during takeoff. The number one and myself had to hold on to carts so they wouldn't roll. Bottom line is the Captain never said 'prepare for departure.'Captain must say prepare for departure...if he doesn't we might think that chime was just a call light or something of that nature.




Synopsis: Flight attendant reported that the Captain did not notify the cabin crew before takeoff; resulting in a departure with flight attendants standing in the galley.
Date: 201209
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: TRACON ZZZ
Second aircraft: Saab 340 Undifferentiated
Reporter organization: Government
Reporter function: Approach; Departure
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While I was conducting training on the position; my Developmental was vectoring a CRJ-700 at 8;000 for sequencing to the [STAR]. There was a Saab 340 stacked underneath the CRJ-700 at 7;000. A Pilatus PC-12 was an overflight at 8;000 going direct. My Developmental stopped the CRJ-700 at 8;000 from the [STAR] profile descent reference the Saab 340 at 7;000; but got caught up with issuing speed control on arrivals being switched to final; and forgot to turn the CRJ-700. I let the situation go too long before instructing the Developmental to take action. Recommendation; better control of the position. The Developmental is in the late stages of training on this position; working on extended hours and I didn't want to break in. I should have made a mention of the developing situation sooner in a more; 'don't forget about [the PC-12] out there at 8; 000;' providing information only; and still allowing time to take action. It is a tough line when letting a developmental work through tough traffic situations. You don't want to override them; or say something too soon. You want them to recognize the traffic. Being overbearing on the position can work to your disadvantage. But being extremely vigilant is my responsibility and taking action to ensure separation is being maintained is my job. I will be more pro-active in pointing out traffic to the Developmental and taking action sooner.




Synopsis: TRACON Controller providing OJT was late in issuing guidance to the Developmental resulting in a loss of separation.
Date: 201204
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Dawn
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic System Lines; Connectors; Fittings
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown; Workload; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Hydraulic Y failure [event; so] had equipment standing by in case of further failures upon landing. Normal landing. Terminated emergency with Tower after landing and proceeded to gate.

Callback: The Reporter stated that the Yellow Hydraulic System had an apparent complete hydraulic fluid loss because of system failure somewhere. He had no idea what failed but the aircraft had fluid all along the aircraft's fuselage after landing.



Synopsis: During climb; an A319 ECAM alerted HYD Y RSVR LO LVL; so an emergency was declared. After a normal landing; the emergency was terminated.
Date: 202107
Local time of day: 1801-2400
Location: ABQ.TRACON, NM
Flight conditions: VMC
Light: Night
Aircraft: Small Transport; Low Wing; 2 Turboprop Eng
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class D AEG
ATC / advisory: Tower ABQ
Reporter function: Pilot Flying; Captain; Check Pilot; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance; Flight Crew Took Evasive Action; Flight Crew Became Reoriented
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: In bound to Runway 8; cleared for the visual approach and through Double Eagle's airspace. I continued towards the runway and was told by tower they received a low altitude alert. I was aware of the surrounding terrain and obstacles and was never in doubt of the continued safe operation of the flight. I did; however climb a few hundred feet (for a short bit) just for the sake of a response to the towers comment.




Synopsis: Pilot reported receiving a low altitude alert from ATC while on a visual approach.