elihoole/asrs-aviation-reports huggingface dataset:
Date: 201405
Local time of day: 1801-2400
Location: ZAB.ARTCC, NM
Flight conditions: VMC
Light: Daylight
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZAB
ATC / advisory: Center ZAB
Second aircraft: B737 Next Generation Undifferentiated
Reporter organization: Air Carrier
Reporter function: First Officer
Second reporter function: Captain
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; General Physical Injury / Incapacitation
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: While descending through FL290 on the EAGUL Five RNAV Arrival into PHX; we encountered unexpected wake turbulence that put the aircraft into a 20-degree right bank followed by a 20-degree left bank. There were no reports of turbulence in the area. We noticed another aircraft descending ahead of us approximately 20 miles ahead and 2;000 FT below. We queried ATC told them what happened and asked what kind of aircraft were we following. They told us it was another B737NG. He gave us a 15-degree heading change to the right in order to put more distance between us and the other aircraft. After a few minutes; we were cleared back on course and had no other wake turbulence issues. Once we were sure that the aircraft was under control; the Captain called the cabin to check on the flight attendants. They stated that [one] Flight Attendant had felt a jolt in her neck and felt that she may have twisted wrong during the event. Once on the ground; the Captain reported the incident as per the FOM and spoke to the [injured] Flight Attendant at length. She assured us that she was okay and continued the trip. We continued the remainder of the trip with no other incidents. I'm not sure if there was much that could have been done in this event. We just happened to get caught up in wake turbulence. However; we did have a direct headwind on the arrival. That could have been the cause of the wake not dissipating soon enough. I will now be more aware of the potential hazards of encountering wake even though we have 20 miles of separation especially when there is a strong headwind along the flight path.


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


Synopsis: B737-800 flight crew reported encountering wake turbulence in trail of another B737NG on descent to PHX.
Date: 201205
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Distraction; Situational Awareness; Time Pressure
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: In cruise flight at FL250; there was a sudden 'pop' noise and felt pressurization stop. EICAS indicated PACK 1 Fail. The cabin pressure altimeter started to increase. I had contacted ATC and notified them I needed to descend immediately. ATC responded clear to FL200. I said no; I need 10;000 FT and I was then cleared. We as a crew put on the O2 mask and established crew communication and began our rapid descend ER memory items. As we were descending I had notified the flight attendant of the ER and to prepare the cabin for arrival. She asked if she needs to deploy the passenger O2 masks and after seeing the cabin altitude begin to stabilize and not had gone above 9;800; I said no. I had ACARSed company that we were diverting. ATC told us that airport was just 20 miles behind us and they gave us initial vectors. Once we got down to 10;000 FT; we cleaned the aircraft up (gear up; spoilers stowed) and took our O2 masks off. We then performed normal checklists of weather in range and approach checklist and proceeded to the divert airport. Once cleared to land; we had the Airfield Rescue and Fire Fighters follow us and do a thermal scan of the aircraft for hot spots and check the brakes because of a possible over weight landing. Once given the OK; we taxied to the terminal and debriefed the crew; passengers and company.




Synopsis: An EMB-145 EICAS alerted PACK 1 FAIL; and as the cabin altitude began rising the crew declared an emergency; descended to 10;000 FT; completed the QRH and diverted to a nearby airport.
Date: 202007
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Sail Plane
Operator: Government
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Second aircraft: Cessna Single Piston Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Pilot Not Flying; Flight Engineer / Second Officer; Other / Unknown
Reporter qualification: Flight Crew Flight Engineer; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Communication Breakdown
Second reporter function: Instructor; Pilot Flying; Single Pilot
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Flight Crew; Person Observer
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: As the last training sortie of the day; our organization aero-towed Aircraft X to an altitude of 200 ft. AGL in order to practice a low altitude rope break (PTT). Prior to departing; it was announced on CTAF that our aircraft would return immediately to the same runway and land in the opposite direction as an emergency aircraft. During the maneuver; Aircraft Y was waiting for takeoff on the end of the runway. After landing our glider rolled into the intersection of the two runways and completed a turn SW onto Taxiway in order to wait for the recovery team to arrive in the golf cart.After announcing on CTAF the crossing of Runway; our golf cart team proceeded to recover the glider in the intersection of Runway and Taxiway. As we crossed we heard Aircraft Y announce commencing a takeoff on CTAF. Being aware that our glider was still in the runway safety area of the runway; we announced 'STOP; STOP; STOP the takeoff roll' on CTAF. Regardless of the transmission; the pilot of Aircraft Y continued the take off roll and passed the recovery team by approximately 50 ft.


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


Synopsis: Glider Pilot and Observer reported a Critical Ground Conflict after landing while still in the runway safety area with departing traffic.
Date: 201302
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Rudder Pedal
Reporter organization: Personal
Reporter function: Single Pilot; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Regained Aircraft Control; General Maintenance Action
Contributing factors: Human Factors; Aircraft
Primary problem: Ambiguous

Narrative: I was flying the ILS for guidance for a visual landing.  Winds where light at about four knots.  Landing was normal at main gear touchdown but as soon as nose wheel contacted the runway the aircraft snapped to the left.   I applied full right rudder and applied right brake in an attempt to correct the aircraft back down the runway.  None of this was effective in correcting the situation.  Departed the runway to the left side and was able to miss the taxiway sign and all obstructions; I thought.  I was able to taxi off the grass and back to the FBO ramp.  On shut down I noticed metal missing on one prop blade and notified the Tower to check for a light that might have been hit.  They called me back shortly and did confirm I had struck one light.  I do not feel that this was pilot induced due to the weather and my experience.  However; my Mechanic will be inspecting the aircraft for any maintenance issues the coming week.  At this time the reason for the runway departure is unknown.

Callback: The reporter states that no deficiencies could be found with the brakes or nose gear after the incident.  The engine has been removed for overhaul so the aircraft has not been taxied or flown since.  The reporter believes that the only explanation for the loss of control is that his passenger; a large non pilot; may have gotten his foot on the rudder pedal at touch down.



Synopsis: C182 pilot lost control of his aircraft when the nose wheel is lowered to the runway after a normal main gear touch down.  A runway light is struck by the propeller during the runway excursion; but the reporter is able to regain control and taxi back to the ramp.
Date: 201212
Local time of day: 1801-2400
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Flight plan: IFR
Mission: Passenger
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Anomaly: Deviation / Discrepancy - Procedural Other / Unknown; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: Pre-flight
Contributing factors: Company Policy; Procedure; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: During briefing; the Captain informed me that the Sabre Flight Planning system did not calculate the required fuel correctly for the ETOPS airport. Fuel required was showing 49;064 LBS in the ETOPS page. On the flight plan; the ETOPS fuel showing was 47;719 LBS on release number 2. I amended to release 3 prior to departure to add fuel for the three alternate solution.




Synopsis: Dispatcher reports being informed by the Captain involved that the Sabre Flight plan has an error in the ETOPS fuel required.
Date: 201302
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna 402/402C/B379 Businessliner/Utiliner
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Electrical Power
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Situational Awareness; Training / Qualification; Troubleshooting; Workload
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I detected smoke in cockpit; ran emergency checklist; declared an emergency; and informed ATC that I would be shutting the electrical system down after I made clear my intentions. I then continued after smoke stopped to the closest and suitable airport. I then landed and taxied in with no further issues.




Synopsis: A C402 Captain detected smoke in the cockpit. He declared an emergency; notified ATC that he was securing his electrical system; and landed at the nearest suitable airport.
Date: 201205
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Flap Control (Trailing & Leading Edge)
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Landed in Emergency Condition; General Maintenance Action; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Unable to extend flaps during approach and flap indicator showed very slight split flap (asymmetry) with flap handle in the UP position. Executed missed approach and advised ATC. Ran appropriate checklists and concluded that a no flap/slat landing was required. Declared emergency with ATC; requested ARFF to stand by; contacted company; sent message to Dispatch. Approach and landing were uneventful. Described problem to Maintenance Supervisor and made entries in logbook.


Second narrative: On final; Captain called for flaps 1 then flaps 5. Noticed that flaps indicator indicated 0 flaps with a slight split to the indicator. Checked slat indication and they indicated up. Checked hydraulics; indication was normal. Captain asked for a go around. Proceeded to hold at 3;000 FT and follow QRH procedures. After QRH procedure was completed; Planed on a no flap landing. Declared an emergency and asked for ARFF equipment. Landed without further incident.


Synopsis: B737 flight crew reports inability to extend trailing edge flaps during approach. A go around is initiated; an emergency is declared; and the QRH is consulted resulting in a no flap landing.
Date: 201911
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Air/Ground Communication
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Elderly passenger approximately 70 years old experienced a heart condition episode during our flight from ZZZ to ZZZ1. My understanding that it was possibly related to possible pre-existing conditions of diabetes and/or heart disease. Multiple attempts were made to contact Medlink unsuccessfully until it was too late to risk continuing the flight to ZZZ1 and therefore a diversion was made. Obviously; this was an old [aircraft] that had no SATCOM.This event began about 160 miles prior to destination. We had very little time to make the diversion decision without the aid of a Medlink professional; therefore for the safety of the passenger and the lack of any other expert opinion or information; the diversion was made to ZZZ. The stress and complexity of this situation was increasingly compounded by the frustrating failure to contact Medlink. NO AIRINC FREQUENCY WORKED. We tried multiple frequencies; and at least a couple other frequencies that were suggested to us by Dispatch and other company aircraft attempting to help us. Obviously; this was an old [aircraft] that had no SATCOM or we would have used that. Get SATCOM on all planes.




Synopsis: Air carrier Captain reported being unable to contact medical via SATCOM creating a divert event for an ill passenger.
Date: 201512
Local time of day: 0001-0600
Location: STL.Airport, MO
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground STL
Reporter organization: Air Carrier
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion
Anomaly: ATC Issue All Types
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Chart Or Publication
Primary problem: Chart Or Publication

Narrative: There is a discrepancy between the 10-9; 10-9B; and 10-9D Jepp Charts for STL and what the actual taxiway signage shows. On the charts; the taxiway between N and M along C/D is shown as D2. The signage on the ground shows this same taxiway as D5.




Synopsis: Air carrier First Officer reported the taxiway between Taxiway D and the ramp; between Spot 9 and 10 is labeled as D5 on airport signage and on the 10-9 airport diagram but labeled as D2 on the 10-9B and 10-9D charts.
Date: 201310
Local time of day: 1201-1800
Location: BOS.Airport, MA
Flight conditions: VMC
Light: Dusk
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Landing
ATC / advisory: Tower BOS
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not 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
Detector: Person Flight Crew
When detected: In-flight
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Ambiguous

Narrative: BOS Tower requested an early turn off or expidited clearance of an intersecting runway. The First Officer flying landed and applied heavy braking in an attempt to clear the runway at the requested turnoff. Due to the aircraft having a full pax load and a tailwind on landing the First Officer did not anticipate the aircraft to decelerate slowly.  An attempt to make the taxiway late and fast made me take control from the First Officer after recognizing we were heading towards the runway/taxi lights. I applied max braking and stopped the aircraft on the intersection of the taxiway and runway short of the lighting. The aircraft never left the runway or taxiway; but was in a position that turning back onto the runway; did not give me confidence that the main gear would clear lighting in the turn. I requested assistance from the Tower to observe the turn to avoid contact with the lights or movement off the taxiway. A BOS airport ops driver assisted by monitoring our turn back on to the runway. No additional assistance was reqested by us or the Tower and we proceded to the gate. Landing heavy with a tailwind and attempting a maximum performance and expidited runway departure was not expected from a new pilot without further briefing by him or myself. Do not accept any clearance if there is any question wheather or not it is possible to accomplish the clearance. Fully brief any exceptions or conciderations taking into account the experience level of the pilot.




Synopsis: A319 Captain reports a near runway excursion with the relatively new First Officer landing and attempting to accommodate an ATC request to clear the runway quickly.
Date: 201910
Local time of day: 0601-1200
Location: MKE.Airport, WI
Flight conditions: IMC
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Airspace: Class C MKE
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Maintenance
When detected: Taxi
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were getting ready to push off the gate. We contacted Ground Control for the clearance to push onto the active taxiway. All checklist items were complete. I then told the ramp personnel that they were cleared to push back into the taxiway. There was a loud thud and bang. The ramp told us the tow bar shear pin had sheared and struck the nose gear. I looked down and found the parking brake to still be set. I thought the brake was off. We called maintenance immediately. They had to take the plane back to the hanger. I filled out the company report and didn't even think that this incident was reportable. Upon contacting our pilot rep before an upcoming meeting with management they said we should file a report. Had I known this event was under the umbrella; I would have filed it immediately. This sort of event can happen when becoming complacent and taking the normalcy for granted.




Synopsis: CRJ-700 pilot reported that they forgot to release brakes during pushback; resulting in a flight delay and maintenance action.
Date: 201212
Local time of day: 0601-1200
Location: PCT.TRACON, VA
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZZZ
ATC / advisory: TRACON PCT
Aircraft component: FMS/FMC
Component problem: Design; Improperly Operated; Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Human factors: Workload; Time Pressure; Confusion; Distraction
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: We were distracted by the two FRDMM fixes that were in the FMS for the FRDMM 1 arrival and in attempting to be sure we deleted the right one (due to the fact that the first FRDMM would've had us flying in the completely wrong direction). I had my head down and I did not have a descent rate set that would ensure we crossed MORLL between FL200 and 17000. We crossed MORLL at FL211.The FMS needs to be fixed. Next time I will transfer controls to the First Officer so he/she can monitor the descent while I correct the malfunction in the FMS.


Second narrative: While on the FRDMM 1 we were distracted trying to delete the proper FRDMM fix from the FMS. Due to the distraction and tailwind we did not make the crossing restriction of FL200 at FRDMM. We advised ATC that we were too high; and they confirmed that there was no violation.Modify the FMS to eliminate the need to remove the duplicate fix.


Synopsis: An ERJ crew on the DCA FRDMM 1 Arrival was deleting duplicate FRDMM FMS waypoints and failed to begin the descent which caused the aircraft to cross MORLL at FL211 instead of FL200.