Narrative:

I was working mostly student pilots on practice approaches and practice holding. The weather was building off the departure end of sfb departure end of the 9L & 9R. Aircraft X came from sector K or sector D and should have come over at 040 as per the LOA; but came over at 030. I did notice that aircraft X was not at the correct altitude; I knew it might be an issue; but I didn't feel a sense of urgency to climb the flight to 040 and had other things going on.the majority of my attention was focused on the west side of sfb. Arrivals for orl were entering my airspace from the north and I was flowing them southwest over the sfb final and to the D sector; which is responsible for working them into orl. I identified aircraft Y climbing off of sfb and turned the aircraft north and away from the precipitation which was building to the east. When I issued the 360 heading; I did not evaluate the proximity to aircraft X. Frankly; I had been working at a high level for a long period; but was waiting for the traffic to die down. More and more IFR releases were flashing from sfb and I was definitely getting the feeling of reaching the edge of my skill level. I did ask for the sector to be split; but by that time I had already had an error. I was under the impression that the flight schools would not be operating at full capacity because of the coronavirus epidemic; but they were out in full force. I should have asked for help sooner. I should have asked for the sector to be split about 30 minutes sooner. Once the sector was split; traffic was easily manageable. Even in times of normal staffing; I feel there are never enough controllers to split sectors without running long position times.

Related reports:

Google
 

Original NASA ASRS Text

Title: F11 TRACON Controller reported a conflict after an aircraft came over at the incorrect altitude.

Narrative: I was working mostly student pilots on practice approaches and practice holding. The weather was building off the departure end of SFB departure end of the 9L & 9R. Aircraft X came from Sector K or Sector D and should have come over at 040 as per the LOA; but came over at 030. I did notice that Aircraft X was not at the correct altitude; I knew it might be an issue; but I didn't feel a sense of urgency to climb the flight to 040 and had other things going on.The majority of my attention was focused on the west side of SFB. Arrivals for ORL were entering my airspace from the north and I was flowing them southwest over the SFB final and to the D sector; which is responsible for working them into ORL. I identified Aircraft Y climbing off of SFB and turned the aircraft north and away from the precipitation which was building to the east. When I issued the 360 heading; I did not evaluate the proximity to Aircraft X. Frankly; I had been working at a high level for a long period; but was waiting for the traffic to die down. More and more IFR releases were flashing from SFB and I was definitely getting the feeling of reaching the edge of my skill level. I did ask for the sector to be split; but by that time I had already had an error. I was under the impression that the flight schools would not be operating at full capacity because of the Coronavirus epidemic; but they were out in full force. I should have asked for help sooner. I should have asked for the sector to be split about 30 minutes sooner. Once the sector was split; traffic was easily manageable. Even in times of normal staffing; I feel there are never enough controllers to split sectors without running long position times.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.