This article is based on an official press release from Green Taxi Aerospace and background data provided in the source material.

Green Taxi Aerospace Secures Critical FAA Concurrence for Electric Taxi System

Green Taxi Aerospace has achieved a significant regulatory milestone in its bid to decarbonize ground operations, receiving official concurrence from the Federal Aviation Administration (FAA) on its certification plan. This agreement validates the company’s roadmap for its “Zero Engine Taxi” (ZET) system, a retrofit technology designed to allow airliners to taxi without using their main jet engines.

According to the company’s announcement, this concurrence effectively “de-risks” the development program. By aligning with regulators on testing and compliance strategies before the final conforming prototype is built, Green Taxi Aerospace aims to avoid the costly re-engineering pitfalls that have plagued previous attempts at electric taxiing solutions. The approval clears the path for the company to transition from planning into detailed design and hardware fabrication.

The Plano, Texas-based startup, led by former F-16 pilot David Valaer, is targeting a Supplemental Type Certificate (STC) for the Embraer E175 regional jet by late 2027.

Regulatory Alignment Before “Cutting Metal”

In the complex world of aerospace certification, FAA concurrence is a vital “gate” event. It signifies that the regulator has reviewed and accepted the manufacturer’s proposed methods for demonstrating safety and airworthiness. For Green Taxi Aerospace, this means the specific tests and data required to prove the system is safe are now agreed upon.

CEO David Valaer emphasized the strategic importance of this patience-first approach in the company’s statement:

“We touch the APU, we touch the landing gear, we touch the pilot control system. It’s a very complicated project… We’re not going to cut metal until our data is approved by the FAA.”

, David Valaer, CEO of Green Taxi Aerospace

With the certification plan approved, the company has outlined its immediate schedule. Detailed design drawings are slated for completion by mid-2026, followed by the assembly of the first “conforming” prototype, built exactly to the certified design standards, in late 2026. Ground taxi tests on an Embraer E175 are scheduled to begin in 2027.

The “Zero Engine Taxi” Technology

The core of Green Taxi Aerospace’s innovation is a retrofit system that installs electric motors directly onto the aircraft’s main landing gear. Unlike traditional taxiing, which relies on the thrust of massive jet engines optimized for flight, the ZET system uses the aircraft’s existing Auxiliary Power Unit (APU) to power the wheels.

The APU is a small turbine engine located in the tail of the aircraft. While it burns fuel, it is significantly more efficient at ground speeds than main engines. By utilizing the APU, the aircraft can push back from the gate and taxi to the runway with its main engines turned off.

Projected Operational Savings

Green Taxi Aerospace has released data highlighting the potential efficiency gains for operators of the Embraer E175. Regional jets are the primary target because they perform frequent flights with high daily taxi times, maximizing the utility of the system.

According to company projections:

• Fuel Savings: Approximately 80,000 gallons per aircraft, per year.
• Cost Reductions: Estimated savings of $250,000 to $350,000 per aircraft annually, factoring in fuel and maintenance.
• Emissions: An 85% reduction in ground-level carbon emissions compared to single-engine taxiing.

Crucially, the system is designed to be lightweight. The company states the total system weight is under 300 lbs. This is a critical metric; if the system is too heavy, the fuel burned carrying the extra weight during flight could negate the savings achieved on the ground.

Strategic Partnerships

To navigate the certification process, Green Taxi has partnered with StandardAero, a major aerospace maintenance, repair, and overhaul (MRO) provider. StandardAero is leading the certification effort, a move Valaer describes as essential for credibility.

“This partnership with StandardAero positions us for success by aligning our innovative technology with a proven certification partner.”

, David Valaer, CEO of Green Taxi Aerospace

Additionally, the company is collaborating with Delta Air Lines through its “Sustainable Skies Lab” to validate operational data, ensuring the technology meets the rigorous demands of a major commercial carrier.

AirPro News Analysis

Contextualizing the Competitive Landscape

While the concept of electric taxiing is not new, Green Taxi Aerospace’s approach attempts to solve the specific engineering hurdles that stalled previous ventures. In 2013, the EGTS joint venture between Safran and Honeywell attempted a similar main-gear concept. However, that system reportedly weighed over 600 lbs and required extensive airframe modifications, which ultimately destroyed the business case.

Green Taxi’s claim of a sub-300 lb system suggests significant advancements in electric motor density over the last decade. By keeping the weight low, they address the primary failure point of the EGTS program.

The company also faces different competition than its predecessors. WheelTug is developing a system that places motors in the nose gear. While this simplifies installation, the nose gear carries less weight, which can limit traction in icy conditions or on slopes. Green Taxi’s decision to power the main gear offers better traction but represents a more complex integration challenge.

Another alternative, TaxiBot, uses semi-robotic tugs to tow planes. While this requires no aircraft modification, it introduces logistical complexity at busy airports, as tugs must return to the gate after every departure. Green Taxi’s onboard solution avoids this congestion but places the capital cost and weight penalty directly on the airline.

With FAA concurrence now secured, Green Taxi Aerospace has cleared the first major hurdle in proving that a lightweight, onboard electric taxi system is not just theoretically possible, but commercially viable.

Sources:
Green Taxi Aerospace Press Release
StandardAero
Delta Sustainable Skies Lab

NTSB Issues Preliminary Report on Fatal Socata TB21 Crash in Arizona

The National Transportation Safety Board (NTSB) has released its preliminary report regarding the fatal crash of a Socata TB21 Trinidad near Prescott, Arizona. The incident, which occurred on the evening of February 4, 2026, resulted in the death of the pilot, who was the sole occupant of the aircraft. The report establishes a factual timeline of the flight’s final minutes, focusing heavily on communications between the pilot and air traffic control at Prescott Regional Airport (PRC).

According to the NTSB documents, the single-engine aircraft (Registration N967WM) was conducting a visual approach at night when it impacted terrain approximately two miles north of the runway. While the preliminary report details the sequence of events leading up to the crash, it does not yet determine a probable cause. Investigators are continuing to examine pilot history, aircraft maintenance, and environmental factors.

Flight Timeline and ATC Communications

The NTSB report outlines a specific chronology of the flight, which originated from John Wayne Airport (SNA) in Santa Ana, California, at approximately 4:50 PM PST. The flight proceeded to Arizona without incident until the approach phase into Prescott.

Arrival at Prescott

At 7:44 PM MST, the pilot contacted Prescott Tower to announce his intent to land. The tower controller initially instructed the pilot to maintain an altitude at or above 6,500 feet Mean Sea Level (MSL), cross over the airport, and enter a left downwind leg for the runway. The pilot acknowledged these instructions and proceeded to fly over the airport as directed.

The Final Maneuvers

Shortly after the initial approach began, the tower controller updated the instructions. At 7:47 PM MST, the controller advised the pilot that the altitude restriction was canceled and instructed him to extend his downwind leg. The controller stated that the tower would call the pilot’s base turn, the turn required to align the aircraft with the runway for landing.

Approximately 46 seconds after the instruction to extend the downwind leg, the controller issued a traffic advisory regarding another aircraft on final approach. The NTSB report notes:

“The pilot acknowledged this caution. This acknowledgment was the last communication from the aircraft.”

Radar contact was lost shortly after this transmission while the aircraft was maneuvering north of the airport. The wreckage was subsequently discovered in open terrain near Poquito Valley.

Wreckage and Environmental Conditions

The crash site was located in a remote field roughly two miles north of the runway threshold. First responders and NTSB investigators described the scene as a scattered debris field, consistent with a high-energy impact. The aircraft was destroyed upon impact.

Weather data included in the report indicates that the flight was operating under Visual Meteorological Conditions (VMC). Skies were reported as clear with good visibility, suggesting that adverse weather was likely not a primary factor. However, the crash occurred during hours of darkness in an area known for sparse ground lighting.

AirPro News Analysis

While the NTSB has not yet assigned a cause, the factual details regarding the “extended downwind” instruction at night are significant. In aviation safety, extending a downwind leg at night in mountainous terrain can expose pilots to spatial disorientation or controlled flight into terrain (CFIT), particularly if ground lighting is insufficient to provide a visual horizon. This phenomenon, often called the “black hole effect,” is a known risk factor for night approaches into airports surrounded by unlit terrain.

The Socata TB21 is a complex, high-performance aircraft. Managing a delayed base turn while monitoring traffic and maintaining terrain clearance at night imposes a high cognitive load on a single pilot. Future investigative updates will likely focus on whether the extended path took the aircraft into an area of rising terrain or if the pilot lost situational awareness during the maneuver.

Investigation Status and Next Steps

The current document is a preliminary fact-finding report. The NTSB emphasizes that it does not contain analysis or a determination of probable cause. A final report, which will include the board’s official conclusions, typically takes 12 to 24 months to complete.

Moving forward, investigators will focus on several key areas:

• Pilot Background: A review of the 64-year-old pilot’s training, medical certification, and potential fatigue factors.
• Mechanical Integrity: An examination of maintenance logs, the engine, and flight controls to rule out mechanical failure.
• ATC Handling: An analysis of the timing of the controller’s instructions, specifically the command to extend the downwind leg and the management of traffic separation.

Frequently Asked Questions

What is a Preliminary Report?

A preliminary report is an initial document released by the NTSB shortly after an accident. It contains factual information gathered on-scene, such as flight times, weather conditions, and wreckage location, but does not analyze the data or determine why the accident happened.

When will the cause of the crash be known?

The NTSB typically releases a final report, which includes the probable cause, 12 to 24 months after the accident. This allows time for detailed forensic analysis of the wreckage and review of all operational factors.

Was the weather a factor?

Current reports indicate the flight was operating in Visual Meteorological Conditions (VMC) with clear skies. However, the lack of daylight and the terrain environment are factors investigators will consider regarding visibility and spatial orientation.

Sources

• NTSB Preliminary Report

This article summarizes reporting by 12News and journalist Adam Correa.

Small Plane Crashes into North Phoenix Neighborhood; Three Injured

A single-engine aircraft crashed into a residential neighborhood in North Phoenix on the morning of Wednesday, March 4, 2026, injuring three people and damaging two homes. According to reporting by 12News, the incident occurred near the intersection of Deer Valley and Cave Creek roads as the plane attempted to return to the nearby airport.

Emergency responders arrived at the scene in the 2000 block of East Parkside Lane shortly after 7:30 a.m. MST. The aircraft, identified by authorities as a Piper PA-28, struck the roof of one residence before coming to rest in the backyard of a neighboring property. While the crash caused significant structural damage and a fuel leak, officials have confirmed there were no fatalities.

Incident Timeline and Flight Details

The crash occurred during the morning rush hour, a time when many residents were still at home. Preliminary information cited by local outlets indicates that the aircraft had recently departed from Deer Valley Airport (DVT), one of the busiest general aviation airports in the world.

Attempted Return to Airport

According to the Federal Aviation Administration (FAA), the pilot appeared to be attempting a return to the airfield shortly after takeoff. While the National Transportation Safety Board (NTSB) has not yet determined a probable cause, an immediate return to the airport often suggests a mechanical anomaly or onboard emergency. The Piper PA-28 is a common trainer aircraft, and reports confirm that a flight instructor and a student pilot were the two occupants on board.

Injuries and Property Damage

The Phoenix Fire Department responded rapidly to the scene to manage potential fire hazards and treat the victims. Three individuals were transported to local hospitals.

Occupants and Residents

Both the flight instructor and the student pilot survived the impact. They were transported in stable condition with injuries described by responders as cuts and burns. On the ground, one resident, a homeowner, was also injured. Reports suggest the resident was either inside the home or in the backyard at the moment of impact; they were hospitalized as a precaution.

Structural Impact and Hazmat Response

The collision caused distinct damage to two separate properties. The plane clipped the roof line of the first home before crashing into the second home’s yard. The impact ruptured the aircraft’s fuel tanks, causing fuel to leak into the attic of one of the structures. Hazmat crews were deployed to contain the spill and prevent environmental contamination or fire.

“Situations like this when you do have multiple residences involved… it is a miracle that no one was [seriously] injured.”

— Phoenix Fire Department spokesperson

Investigation and Safety Context

Federal investigators from the NTSB and FAA are currently on-site to document the wreckage and determine the sequence of events leading to the crash. The investigation will likely focus on engine performance, pilot communications with air traffic control, and weather conditions at the time of the flight.

Deer Valley Airport Operations

Deer Valley Airport handles over 400,000 flight movements annually, heavily driven by flight training operations. The surrounding area is densely populated, creating a complex interface between urban residential zones and aviation activities. While crashes in these neighborhoods are statistically rare given the volume of traffic, this incident follows a pattern of occasional emergency landings in the open lots and streets surrounding the airport.

AirPro News Analysis

Training density and urban planning: The survival of all involved in this crash highlights the crashworthiness of modern general aviation airframes, but it also underscores the risks inherent in the “urban interface” of busy training airports. Deer Valley Airport was once surrounded by open desert, but Phoenix’s rapid northward expansion has encircled the facility with residential housing.

When training aircraft suffer power loss on takeoff, the most critical phase of flight, pilots have very few options if they cannot glide back to the runway. In this instance, the pilot’s attempt to turn back, a maneuver known to be high-risk at low altitudes, suggests the situation was critical. The lack of fatalities is indeed fortunate, but this event will likely renew local discussions regarding flight path zoning and safety buffers in North Phoenix.

Sources

• 12News
• Federal Aviation Administration
• Phoenix Fire Department