First I will point out that melee players have been clasically taught to fastfall their aerials after the hitlag that results from hitting an opponent or a shield. While this is a very consistent method, it is not always the best thing to do in any given situation. In the case of falco doing a mid-height aerial, he can maximize frame advantage by fastfalling before the first active hitbox of the attack comes out. His short hop can be fastfalled beginning on frame 13. To get the lowest possible aerial (and thus, the maximum frame advantage on an opponent's shield) it is necessary to fastfall on the first frame possible, but executing this can be tricky! If you go for this optimal timing and are not frame perfect, you might end up inputting the fastfall too late, at which point your character is undergoing hitlag and your fastfall input will not register. If you do it a little early however, the game has a generous 3 frame buffer during which simply holding down will result in a fastfall on the first possible frame.
I would imagine that none of this seems particularly important to a lot of people who understand the game reasonably, as falco's mid-height nair approaches are generally pretty safe. The optimal fastfall timing is clearly much more delayed than the typical post-hitlag timing, however, and once I realized this I decided to test the frame data for myself. Here is what I came up with:
The following table is for inputting the fastfall so that it occurs the first frame possible AFTER hitlag:
| Frame of SH that falco inputs nair | Frame advantage on shield |
|---|---|
| 8 | -5 |
| 9 | -4 |
| 10 | -4 |
| 11 | -4 |
| 12 | -3 |
| 13 | -3 |
| 14 | -3 |
| 15 | -3 |
| 16 | -2 |
| 17 | -2 |
| 18 | -1 |
| 19 | -1 |
| 20 | 0 |
I only listed up to frame 20 of the SH because 0 is the maximum frame advantage falco can achieve from his nair.
The next table is for inputting a fastfall BEFORE hitlag occurs from the nair hitting the opponent's shield. To be clear, this means that the fastfall is inputted during the startup frames of the nair. The first frame falco can fastfall is frame 13 of his short hop as I mentioned above, Because of the 3 frame buffer, it is possible to buffer the fastfall the frame after inputting nair for the cases of nairing on frames 10 and 11 of your short hop (if you input nair on frame 12 of your short hop and fastfall the next frame, the buffer isn't useful since the next frame is the first frame you could input fastfall anyway). The information listed in the table begins with the first frame that it is actually possible to this method:
| Frame of SH that falco inputs nair | Frame advantage on shield |
|---|---|
| 10 | -3 |
| 11 | -2 |
| 12 | -1 |
| 13 | -1 |
| 14 | -1 |
| 15 | 0 |
So let's try to interpret this data meaningfully, with some context. There are a few aspects of it worth discussing. Clearly this method of fastfalling I have mentioned is not necessary to keep falco safe against shield grab. In fact, it is not even necessary to stay safe against falco shine out of shield or sheik nair out of shield (both of which hit on frame 6). This is clear because the method I described is only useful at frame 10 of the SH; the normal method is -4 if falco nairs on frame 10, which is sufficient time to shine before the opponent can counter attack with the options I named. That said...
1) Despite the fact that the normal method is sufficient for the purposes I named above (beating shield grab, etc), leniency is always preferred. If falco is -4, then he only has 1 frame of leniency with which to time his shine after the nair to tie with a frame perfect shine OoS from an opposing falco, and must be frame perfect in order to beat it. With the method I have described, the aggressing falco now has 2 frames of leniency, with no loss in any other aspect. To reiterate, the method I have described gives the aggressor extra leniency at no cost. In a game like melee where interactions can come down to who was one frame faster than the other, this is *extremely* valuable.
2) Raw frame advantage is inherently valuable. Even if you end up out of shine range after hitting their shield, having an extra 2 frames to potentially chase down an escape option is useful. Alternatively, those are an extra 2 frames you could use to back off after a spaced nair and setup your laser game/other pressure more safely.
3) This is perhaps the most important reason I think this method is beneficial. Rolls are invincible on frame 4, and fox shine out of shield hits on frame 4. With a typical mid-height nair executed anywhere from frames 8-11 of falco's short hop, fox can shine OoS or any opponent can roll away before the shine hits their shield. The latter in particular is very frustrating for falco, as it prevents him from actually forcing them to block and starting his pressure. He is forced to make movement reads on their OoS options, which leaves him vulnerable to counterplay. Even a nair executed with the traditional method on frames 12-15 requires frame perfection for falco to tie with a fox shine OoS, and an opponent can still roll before the shine hits them. Compare this to the method i have described: even a frame 10 nair can tie with a fox shine OoS (and as the aggressor, generally your timings should be better than the defender's). A frame 11 nair directly beats both fox's shine OoS and any roll attempts; a frame 12-14 nair beats those options with 1 frame of leniency!
This information is based on my personal testing in 20xx. I would recommend you test it for yourself, both to see it with your own eyes, as well as to confirm what I listed. It is possible I made a mistake on any individual piece of information, although I am fairly confident in it. At some point this week I will try to stream, and I will make sure to show what the nair looks like. I'll just highlight the relevant part of the stream and post the link later. I think this method of executing aerials with falco is surprisingly difficult, but very feasible. It is definitely something worth learning!
