elihoole/asrs-aviation-reports huggingface dataset:
Date: 201205
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Communication Breakdown; Situational Awareness; Training / Qualification
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Vehicle
Detector: Person Maintenance
When detected: Other During Maintenance
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors
Primary problem: Human Factors

Narrative: I experienced a near fatality by a moving vehicle entering the breezeway from International Gate XX just adjacent to where the [aircraft] tire jacks are stored.  There were numerous LD3 containers parked just at the entrance which blocked the view of incoming traffic.  Breezeway-Alley way issue.




Synopsis: A Line Mechanic reports he experienced a near fatality by a moving vehicle entering the Breezeway-Alley way from an International Gate; just adjacent to where the aircraft tire jacks were stored.
Date: 201901
Local time of day: 0001-0600
Location: ZOA.ARTCC, CA
Weather elements / visibility: Turbulence; 50
Light: Daylight
Aircraft: Gulfstream IV / G350 / G450
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZOA
ATC / advisory: Center ZOA
Reporter organization: Air Taxi
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Communication Breakdown; Confusion; Situational Awareness
Second reporter function: Pilot Not Flying; First Officer
Anomaly: ATC Issue All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: We were flying our first trip using CPDLC (Controller Pilot Datalink Communications). Approximately 78 miles west of the DIALO intersection cruising at FL410. We sent a request for FL430. ATC replied unable due to traffic. [Later] we received the message 'standby your traffic is climbing.' [A few minutes later] we received the message 'your traffic is moving.' Shortly after receiving [that] message we received a message that both I and my First Officer interpreted as a clearance to climb to FL430. We initiated a climb rate of approximately 300 fpm. Passing approximately 41;800 feet we received a message to descend to maintain FL410. We immediately initiated a descent and returned to FL410. [We then] received the message 'maintain FL410. Possible higher once traffic moves.' [Shortly thereafter] we received the message 'climb to and maintain FL430.'Both myself and my First Officer are perplexed with this series of events. We both saw a message which we both interpreted as a climb clearance. We both saw a message instructing us to descend to FL410. Neither of these two messages are stored in the message log.


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


Synopsis: GIV flight crew reported departing cruise altitude without a clearance due to confusion with CPDLC communication.
Date: 201902
Weather elements / visibility: Windshear
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Second reporter function: Flight Attendant (On Duty)
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Inflight Event / Encounter Unstabilized Approach; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Attendant
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; General Physical Injury / Incapacitation
Contributing factors: Weather
Primary problem: Weather

Narrative: We had a rejected landing because of wind shear. The plane landed hard and bounced. The Captain immediately took back off. Multiple passengers screamed and began vomiting. Captain made an announcement 5-7 minutes later letting us know the winds were too hard. A jumpseater was hurt. His back was hurt. Once plane landed we went through the cabin to check on the passengers to see that they were okay. Gave out many bags for vomiting. All flight attendants helped. All working flight attendants along with the jumpseater went to the clinic [due to] back pain. [The company] took us off of our trip. My back is hurting a bit and rib area around outside is tight. I was given pain medicine. I was not in pain earlier; however 8 hours later I am a bit sore.


Second narrative: When we landed we experienced a rejected landing because of wind shear. We bounced on the runway twice before getting back into the air. The impact was extremely violent and hard. We were all seated and buckled into the jumpseat. Multiple passengers were vomiting and scared. Once we landed safely we did a walk through to make sure everyone was okay. The jumpseater hurt his back from the hit. All 4 of us working crew went to the clinic because [we] were very stiff and sore in the neck and back areas and [one Flight Attendant] was having chest pains and also a stiff and sore neck and back.


Synopsis: Two air carrier flight attendants reported injuries from a hard landing due to wind shear.
Date: 202112
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
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: Situational Awareness; Time Pressure; Troubleshooting; Distraction; Confusion; Workload
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Executed Go Around / Missed Approach; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: During our flight from ZZZ1 to ZZZ. ATC giving vectors for a visual approach Runway XX. We were using the RNAV (GPS) XX as reference. After ATC gave us a lower altitude (4000 ft.) ATC asked if we have the field in sight to what we answered ''affirmative''. As we continued the descend and due to the GPS approach having different courses from fix to fix we couldn't rely on it as a source of lateral navigation. Once cleared for the approach started to turn inbound towards the runway but the sun (sunlight) was hitting us directly so it impaired a clear visual of the airport; combining this with the rate of descent as we are turning inbound the aircraft gave us the ''terrain; terrain'' aural warnings; we promptly executed an escape maneuver even though we could visually verify that we are clear of terrain. After a go-around we got vectored inbound and continued to an uneventful landing. As suggestion is to maintain awareness to include the sun and sunlight. Even though it was clear skies the sun definitely impaired our vision as we turned towards the runway. Always practice good communication and good judgment with the other pilot. Adhere to FOM and procedures which was what we did and we were safe and landed without an issue.




Synopsis: Air Carrier Captain reported receiving an GPWS Terrain Warning while on approach.
Date: 201602
Local time of day: 1801-2400
Location: JFK.Airport, NY
Aircraft: B737-800
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown; Inflight Event / Encounter Weather / Turbulence
Detector: Person Other Person
When detected: Other post flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Weather
Primary problem: Weather

Narrative: Yesterday I was contacted by the FOQA Gatekeeper in respect to my landing [recently] at JFK. He stated that we might have had a hard landing as FOQA Data indicated that we slightly exceeded the landing gear G limit. The weather at JFK that evening was approximately 300 OVC with gusty winds that upon review for the approach gave us about a 20 to 22 kt crosswind. The approach was nominal with expected turbulence for the given conditions. We were configured and stable all throughout the approach. I was the pilot flying as due to the weather conditions I felt it prudent for me to do the approach and landing. I disconnected the autopilot around 1;000 feet AFL. We broke out slightly above 300 ft. Just prior to crossing the threshold at approximately 85 feet AFL we received a PWS 'go around windshear ahead' warning. I decided to continue the landing not wanting to perform a go around into a possible windshear event as we were on speed and stable with no indications of windshear. I completed the landing and rollout and although not a smooth touchdown it was consistent with the prevailing weather conditions. Nothing in my previous almost 7;000 hrs in the 737 led me to believe it was a hard landing. I really don't have much to add about avoiding a recurrence my decision to land in the face of the late PWS warning would still be the same. Our reception of the warning may have added to my urgency to put the aircraft on the runway and avoid a possible windshear occurrence but how that affected my landing would be speculation on my part.




Synopsis: B737-800 Captain reported that he was advised FOQA data recorded a hard landing at JFK in gusty conditions.
Date: 201507
Local time of day: 0001-0600
Location: NCT.TRACON, CA
Light: Night
Aircraft: UAV - Unpiloted Aerial Vehicle
Operator: Military
Operating under: Part 91
Flight plan: IFR
Mission: Tactical
Flight phase: Climb
Airspace: Class E NCT
ATC / advisory: TRACON NCT
Reporter organization: Government
Reporter function: Departure; Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Aircraft X [a UAV] departed BAB and began a normal climb out to FL190 on their filed route of flight. As Aircraft X was leaving approximately 140 the pilot requested a left 360. I responded with 'Proceed as requested' and restated to maintain FL190. As Aircraft X was about halfway into the unplanned turn the pilot asked if they could rejoin their filed route of flight and climb to FL510 block FL590. I responded with 'Proceed as requested' and did not restate the altitude to maintain. At that point Aircraft X rejoined the filed route of flight and began a climb into ZOA airspace without coordination or communications transfer as the Aircraft X pilot missed the frequency change.I failed to restate the altitude to maintain on the second 'Proceed as requested' instruction. Additionally I will refrain from using 'Proceed as requested' with IFR aircraft as it can lead to confusion. I don't usually use that phraseology with IFR aircraft; but I felt that the pilot was a little confused and that giving them less complicated instructions would be more expeditious. In this case it led to confusion with the altitude and an airspace violation occurred.




Synopsis: NCT Controller reports of an aircraft that requested a 360 turn. The Controller used the term 'Proceed as requested.' The aircraft did and while halfway through the turn the pilot requested to rejoin the flight plan and climb to a higher than assigned block altitude. Controller again used the term; 'Proceed as requested;' but forgot to restate the altitude to maintain. Aircraft climbed through uncoordinated airspace leading to an airspace violation by the NCT Controller.
Date: 202104
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Taxi
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: Vehicle Driver
Human factors: Confusion; Situational Awareness
Anomaly: Conflict Ground Conflict; Critical
Detector: Person Ground Personnel
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: As I was Towing Aircraft X to gate XX. We stopped Supertug XX to let my observer out so he can bring me in ; Aircraft Y began his push off gate XY Nearly clipping wings with my aircraft. I was startle that they began to push that aircraft while I was in the process of parking our aircraft safely at the gate;




Synopsis: Ramp employee reported that while towing an aircraft to the gate; a nearby aircraft began to push back; almost clipping the wings of the aircraft being towed.
Date: 201212
Local time of day: 1201-1800
Location: N90.TRACON, NY
Flight conditions: IMC
Aircraft: Falcon 7X
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E N90
ATC / advisory: TRACON N90
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Other / Unknown; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Manuals; Procedure
Primary problem: Ambiguous

Narrative: On a 090 heading headed east towards the STW VOR we; the crew; believe we were given a descent to 2;000 FT MSL by ATC. At 2;000 FT MSL we received a GPWS caution. ATC instructed us to climb to 3;000 FT. We were constantly monitoring the GPWS and made a climb to 3;000 FT without further incident. We made a follow up phone call with ATC after landing and they said they were in the process of changing the MVA's in that area. They also stated that no further action was being taken in this event. Poor weather in the New York area all morning and afternoon led to high traffic density and radio chatter at the time of the incident.




Synopsis: Falcon 7X Captain experiences a GPWS caution while east bound west of STW VOR at 2;000 FT. ATC issues a climb to 3;000 FT and indicates the MVA in this area is being revised.
Date: 201906
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Aeroplane Flight Control
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Routine Inspection
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors; Procedure
Primary problem: Company Policy

Narrative: Aircraft X came to ZZZ Base Maintenance for an SY6 check. During this check; a [task] was issued for Rudder and Elevator Hinge Line Inspections. This card directs Maintenance to pull off both elevators and inspect hinge fittings. Essentially; all ten fittings on the elevators and at least 6 of the rudder fittings. Then elevators were weighed and reinstalled. Then all three flight controls were rigged. Per [Company guidelines]; this extent of maintenance requires a Functional Check Flight (FCF). A non-routine was generated for the FCF to be completed and was signed off as not necessary by the Supervisor. Non-compliance of [Company guidelines].Supervision re interprets their [Company guidelines] to fit their needs of service. This is one of our governing documents as licensed mechanics and it must be followed. Train supervision and mechanics on what exactly the [Company guidelines] says and how to understand what it says.




Synopsis: Air carrier Maintenance Technician reported Functional Flight Check not accomplished per Company Maintenance Manual requirement.
Date: 201711
Local time of day: 0601-1200
Location: ZZZ.Airport, US
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 C ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Unstabilized Approach
Detector: Automation Aircraft Terrain Warning; Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were descending and we were cleared for the visual. We were high on the approach and I advised ATC that we would extend our downwind to lose some altitude. As we turned base the Pilot Flying still had a high descent rate. I pointed out 2 hills on the approach; which he confirmed he had in sight. The Pilot Flying called for flaps; which were selected. I went heads down for the configuration change. After I [was] heads down for about 5 seconds I looked outside and again pointed out the hills to the Pilot Flying and advised him we were below Glideslope and it looked really low for the approach.Very shortly after that the GPWS system gave us a Terrain Warning. We were daytime and had a visual on the terrain so the Pilot Flying stopped his descent and we continued the approach. A second Terrain Warning triggered shortly after but we confirmed that we had visual on all the terrain. Tower also advised us that they had a low altitude alert and verified that we had the terrain in sight. We elected to continue the approach and made a normal landing.




Synopsis: CRJ-200 Captain reported receiving two GPWS terrain warnings on a day visual approach.
Date: 201911
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Night
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew; Person Flight Attendant
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: About 40 minutes into the flight; the First Officer and I smelled a strong electrical smell in the cockpit. We called the Flight Attendant and asked if she also smelled it. She said that she did and that there was a 'haze' in the cabin air. We [advised] with ATC and completed the QRH items for smoke in the cockpit/cabin. We diverted to ZZZ. After only a few minutes; the smoke cleared and the odor was gone. We decided not to evacuate. After landing; the airport fire department met the plane and conducted an inspection of the exterior and found no sign of fire. The passengers were deplaned and returned to ZZZ1 by bus. The extremely high workload during our diversion was a threat. We were able to complete all checklists and procedures though.


Second narrative: I was Pilot Flying and during climbout; the Captain and I simultaneously noticed a strong smell of electrical issue. Captain ran the QRH and I continued to fly the plane making a descent from FL240 to approximately 9;000 feet. At this time the smell seemed to dissipate; but we continued to divert to ZZZ. The Flight Attendant called and said the smell was strong and there was a haze of smoke that was slightly visible. On short final; the smell came back and we donned our oxygen masks. We made a normal landing.


Synopsis: EMB-145 reported executing a diversion due to strong electrical fumes in the aircraft.