To address the risk management requirements of wake vortex encounters during following aircraft operations， this study proposes an airborne prediction method for wake vortex hazard zones using flight dynamic data of leading aircraft received through automatic dependent surveillance-broadcast in（ADS-B In） equipment. Initially， a leading aircraft’s wake vortex dissipation model and a follwoing aircraft’s dynamic response model are established， employing the induced rolling moment coefficient as the severity indicator for wake encounters and calculating acceptable safety thresholds based on current wake separation standards. Subsequently， a wake vortex hazard zone diffusion model is developed， considering the impacts of turbulence， long-wave instability， crosswinds， and positioning tolerances. Computational analyses are conducted for four operational scenarios： Same-altitude/same-route， same-altitude/crossing-route， different-altitude operations， and closely spaced parallel runway operations. The results demonstrate that utilizing parameters transmitted via ADS-B In equipment （including aircraft type， coordinates， altitude， true airspeed， heading， and wind conditions） enables effective prediction of leading aircraft’s wake vortex hazard zones， facilitating operational risk mitigation and enhancing airborne autonomous flight capabilities. For an A380 aircraft under 3 m/s crosswind conditions， the initial wake vortex hazard zone spans 1 191.12 m horizontally and 1 131.12 m vertically. Lateral intrusion into hazard zones occurs most rapidly， with the transition time from warning zone entry to hazard zone penetration being 1/9 of longitudinal intrusion time and 1/18 of climb intrusion time. In closely spaced parallel runway operations， the critical crosswind speeds for wake influence between a leading A380 and following B747/A320 aircraft combinations are determined as 6.1 and 6.4 m/s， respectively. Increased crosswind reduces longitudinal hazard zone dimensions for both combinations， with greater impact observed in A320 following scenarios.